Writing your first post

Got something worth sharing? The blog is open to every member of the community, and publishing takes about five minutes once you’ve written the thing.

1. Create a file

Add a markdown file to src/posts/. The filename becomes the URL, so fixing-my-starlink-mount.md publishes at /blog/fixing-my-starlink-mount/. Start with frontmatter:

---
title: 'Fixing my Starlink mount'
description: 'A one-sentence summary that shows up in cards, search engines, and RSS.'
date: '2026-06-15'
author: 'Your Name'
tags: ['hardware', 'off-grid']
published: true
---

Set published: false to keep a draft out of the build while you work on it. Reading time is calculated automatically — no need to do the math.

2. Write markdown

Everything you’d expect works out of the box. Headings, bold, italics, links, lists, and:

Blockquotes, for when someone on Slack says something worth framing.

Tables render cleanly:

Trailhead	Elevation	Cell signal
Monarch	11,312 ft	One bar
Cottonwood	12,126 ft	Nope
Marshall	10,842 ft	Surprising

And code blocks come with syntax highlighting:

const neighbors = await slack.users.list();
console.log(`Say hi to ${neighbors.length} valley technologists`);

3. Open a pull request

Push your branch, open a PR against main, and someone will give it a quick review — same as any code change. When it merges, the deploy workflow builds the site and your post is live a couple of minutes later, RSS feed and all.

Stuck on any of this? Ask in Slack. Someone will happily pair on your first post.