<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>riverly</title><description>No description</description><link>https://riverly.gay/</link><templateTheme>Firefly</templateTheme><templateThemeVersion>6.16.8</templateThemeVersion><templateThemeUrl>https://github.com/CuteLeaf/Firefly</templateThemeUrl><lastBuildDate>October 29, 2026 at 10:36:03 PM</lastBuildDate><item><title>Hello world</title><link>https://riverly.gay/posts/hello-world/</link><guid isPermaLink="true">https://riverly.gay/posts/hello-world/</guid><description>One-line summary. Used in post cards, RSS and search results.</description><pubDate>Thu, 29 Oct 2026 00:00:00 GMT</pubDate><content:encoded>&lt;p&gt;This is a post. Everything below the second &lt;code&gt;---&lt;/code&gt; is ordinary Markdown (or MDX if the
file ends in &lt;code&gt;.mdx&lt;/code&gt;).&lt;/p&gt;
&lt;section&gt;&lt;h2&gt;Structure&lt;a href=&quot;#structure&quot;&gt;&lt;span&gt;#&lt;/span&gt;&lt;/a&gt;&lt;/h2&gt;&lt;ul&gt;
&lt;li&gt;&lt;code&gt;##&lt;/code&gt; and &lt;code&gt;###&lt;/code&gt; headings build the table of contents&lt;/li&gt;
&lt;li&gt;&lt;code&gt;- &lt;/code&gt; lists, &lt;code&gt;1. &lt;/code&gt; ordered lists, &lt;code&gt;&amp;gt; &lt;/code&gt; quotes, tables and footnotes all work&lt;/li&gt;
&lt;li&gt;inline &lt;code&gt;code&lt;/code&gt;, fenced blocks, KaTeX math and Mermaid diagrams are supported&lt;/li&gt;
&lt;/ul&gt;&lt;div&gt;&lt;figure&gt;&lt;figcaption&gt;&lt;/figcaption&gt;&lt;pre&gt;&lt;code&gt;&lt;div&gt;&lt;div&gt;&lt;div&gt;1&lt;/div&gt;&lt;/div&gt;&lt;div&gt;&lt;span&gt;const&lt;/span&gt;&lt;span&gt; &lt;/span&gt;&lt;span&gt;example&lt;/span&gt;&lt;span&gt; &lt;/span&gt;&lt;span&gt;=&lt;/span&gt;&lt;span&gt; &lt;/span&gt;&lt;span&gt;&quot;fenced code with a language tag gets syntax highlighting&quot;&lt;/span&gt;&lt;span&gt;;&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;/code&gt;&lt;/pre&gt;&lt;div&gt;&lt;div&gt;&lt;/div&gt;&lt;div&gt;&lt;/div&gt;&lt;/div&gt;&lt;/figure&gt;&lt;/div&gt;&lt;p&gt;Images sit next to the post in an &lt;code&gt;images/&lt;/code&gt; folder and are referenced relatively:&lt;/p&gt;&lt;div&gt;&lt;figure&gt;&lt;figcaption&gt;&lt;/figcaption&gt;&lt;pre&gt;&lt;code&gt;&lt;div&gt;&lt;div&gt;&lt;div&gt;1&lt;/div&gt;&lt;/div&gt;&lt;div&gt;&lt;span&gt;![alt text](./images/example-cover.avif)&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;/code&gt;&lt;/pre&gt;&lt;div&gt;&lt;div&gt;&lt;/div&gt;&lt;div&gt;&lt;/div&gt;&lt;/div&gt;&lt;/figure&gt;&lt;/div&gt;&lt;p&gt;That path is resolved and optimised at build time — do not use &lt;code&gt;/public&lt;/code&gt; URLs for
post images. Files in &lt;code&gt;public/&lt;/code&gt; are served as-is and only belong there for site-wide
assets (favicon, wallpapers, fonts).&lt;/p&gt;&lt;/section&gt;
&lt;section&gt;&lt;h2&gt;Deleting or renaming&lt;a href=&quot;#deleting-or-renaming&quot;&gt;&lt;span&gt;#&lt;/span&gt;&lt;/a&gt;&lt;/h2&gt;&lt;p&gt;Renaming the file changes the URL unless you keep a redirect. Deleting is safe; the
build just drops the entry.&lt;/p&gt;&lt;/section&gt;</content:encoded></item></channel></rss>