<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
  <id>https://riverly.gay/</id>
  <title type="text">riverly</title>
  <subtitle type="text">River&apos;s little corner on the netz</subtitle>
  <updated>2026-10-29T00:00:00.000Z</updated>
  <author><name>River</name></author>
  <link rel="alternate" href="https://riverly.gay/"/>
  <link rel="self" href="https://riverly.gay/atom.xml"/>
  <generator uri="https://github.com/CuteLeaf/Firefly">Firefly v6.16.8</generator>
    <entry>
      <id>https://riverly.gay/posts/hello-world/</id>
      <title type="text">Hello world</title>
      <published>2026-10-29T00:00:00.000Z</published>
      <updated>2026-10-29T00:00:00.000Z</updated>
      <author><name>River</name></author>
      <link rel="alternate" href="https://riverly.gay/posts/hello-world/"/>
      <summary type="text">One-line summary. Used in post cards, RSS and search results.</summary>
      <content type="html"><![CDATA[<p>This is a post. Everything below the second <code>---</code> is ordinary Markdown (or MDX if the
file ends in <code>.mdx</code>).</p>
<section><h2>Structure<a href="#structure"><span>#</span></a></h2><ul>
<li><code>##</code> and <code>###</code> headings build the table of contents</li>
<li><code>- </code> lists, <code>1. </code> ordered lists, <code>&gt; </code> quotes, tables and footnotes all work</li>
<li>inline <code>code</code>, fenced blocks, KaTeX math and Mermaid diagrams are supported</li>
</ul><div><figure><figcaption></figcaption><pre><code><div><div><div>1</div></div><div><span>const</span><span> </span><span>example</span><span> </span><span>=</span><span> </span><span>"fenced code with a language tag gets syntax highlighting"</span><span>;</span></div></div></code></pre><div><div></div><div></div></div></figure></div><p>Images sit next to the post in an <code>images/</code> folder and are referenced relatively:</p><div><figure><figcaption></figcaption><pre><code><div><div><div>1</div></div><div><span>![alt text](./images/example-cover.avif)</span></div></div></code></pre><div><div></div><div></div></div></figure></div><p>That path is resolved and optimised at build time — do not use <code>/public</code> URLs for
post images. Files in <code>public/</code> are served as-is and only belong there for site-wide
assets (favicon, wallpapers, fonts).</p></section>
<section><h2>Deleting or renaming<a href="#deleting-or-renaming"><span>#</span></a></h2><p>Renaming the file changes the URL unless you keep a redirect. Deleting is safe; the
build just drops the entry.</p></section>]]></content>
    </entry>
</feed>
