<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>My Personal Blog</title>
    <link>https://sz97-blog.pages.dev/</link>
    <atom:link href="https://sz97-blog.pages.dev/" rel="self" type="application/rss+xml" />
    <description>Notes, written in markdown, tagged with #hashtags</description>
    <generator>Hugo</generator>
    <language>en</language>
    
    
    
    <item>
      <title>Why I Migrated to Hugo</title>
      <link>https://sz97-blog.pages.dev/posts/260815_why_i_migrated_to_hugo/</link>
      <guid>https://sz97-blog.pages.dev/posts/260815_why_i_migrated_to_hugo/</guid>
      <pubDate>Sat, 15 Aug 2026 00:00:00 &#43;0000</pubDate>
      <description>Why I Migrated to Hugo Wrote up the reasoning mostly for my own future reference, since I know I’ll question this decision again in a year and want the original logic on hand.
The short version: I wanted my writing to live as plain markdown files I could edit from any device, with attachments that stay scoped to the post they belong to, and tags I could just type inline instead of maintaining a separate list. Hugo builds fast, doesn’t need a database, and the templating is flexible enough that I could wire all of that up myself without fighting a plugin ecosystem.
The tradeoff is that anything fancy — comments, search, dynamic filtering beyond client-side tricks — is on me to build. So far that’s been a fair trade.
#Hugo #Meta #Blogging
</description>
    </item>
    
    
    
    <item>
      <title>Sourdough Starter, Week Two</title>
      <link>https://sz97-blog.pages.dev/posts/260810_sourdough_starter_notes/</link>
      <guid>https://sz97-blog.pages.dev/posts/260810_sourdough_starter_notes/</guid>
      <pubDate>Mon, 10 Aug 2026 00:00:00 &#43;0000</pubDate>
      <description>Sourdough Starter, Week Two The starter finally doubled reliably today, which took longer than every recipe promised it would. A few things that seemed to actually matter, as opposed to the things every guide insists matter:
Room temperature swings were the real variable, not flour type. Feeding it at the same time each day mattered more than the exact ratio, at least at this stage. Discarding most of it before each feed felt wasteful right up until it didn’t — a smaller, well-fed culture rises faster than a large, undernourished one. Next milestone is an actual loaf instead of pancakes made from discard.
#Cooking #Journal
</description>
    </item>
    
    
    
    <item>
      <title>A Weekend in the Mountains</title>
      <link>https://sz97-blog.pages.dev/posts/260801_weekend_in_the_mountains/</link>
      <guid>https://sz97-blog.pages.dev/posts/260801_weekend_in_the_mountains/</guid>
      <pubDate>Sat, 01 Aug 2026 00:00:00 &#43;0000</pubDate>
      <description>A Weekend in the Mountains Spent Saturday and Sunday up above the treeline with a borrowed tent and not nearly enough water. Worth it anyway — the ridge trail opens up into a wide bowl of scree and lake that doesn’t show up in any of the photos I’ve seen of the area beforehand, which was half the reason to go.
Trip notes, in case future-me plans this again: start earlier than feels necessary, the parking lot fills up by 8am on weekends. Bring the lightweight stove, not the canister one — altitude makes it sulk.
I kept a running list of gear and mileage for the trip; attached below in case it’s useful for the next one.
trip notes #Travel #Photography #Hiking
</description>
    </item>
    
    
    
    <item>
      <title>Hello World</title>
      <link>https://sz97-blog.pages.dev/posts/260729_hello_world/</link>
      <guid>https://sz97-blog.pages.dev/posts/260729_hello_world/</guid>
      <pubDate>Wed, 29 Jul 2026 00:00:00 &#43;0000</pubDate>
      <description>Hello World This is my very first post on this blog. I set it up with Hugo so that all I ever have to touch again is markdown files like this one — no front matter, just a filename, a heading, and text.
Tags work by just typing a hashtag anywhere in the text, like the ones at the bottom of this post — they show up as a filterable capsule list up top and get quietly removed from the text itself, so they don’t clutter the sentence they were typed in.
Attachments (like the file linked below) live in this post’s own folder under assets/260729_hello_world/ — the folder name matches this file’s name, so nothing else has to be configured.
Here’s an example attachment: my notes . This is a real relative path, so it also works if you open this file directly in Obsidian, iA Writer, or any other markdown editor.
# this looks like a tag but it&amp;#39;s inside a code block, so it&amp;#39;s ignored: #NotATag #HelloWorld #Hugo #Meta
</description>
    </item>
    
    
    
    <item>
      <title>Setting Up Obsidian for This Blog</title>
      <link>https://sz97-blog.pages.dev/posts/260715_setting_up_obsidian/</link>
      <guid>https://sz97-blog.pages.dev/posts/260715_setting_up_obsidian/</guid>
      <pubDate>Wed, 15 Jul 2026 00:00:00 &#43;0000</pubDate>
      <description>Setting Up Obsidian for This Blog Before writing anything else here, I spent an evening getting my note vault configured the way I want it. A few things I landed on:
Turned on automatic link updates, so moving a file around doesn’t quietly break every attachment reference pointing at it. Kept the vault flat where I could — one posts/ folder, one assets/ folder — rather than letting folders multiply per topic. Decided against wikilinks for attachments in favor of plain relative markdown links, since those are the ones that stay readable outside Obsidian too. None of this is complicated, but writing it down once means I don’t have to re-decide it every time I open the vault. #Obsidian #Workflow #Meta
</description>
    </item>
    
  </channel>
</rss>
