Start here: tune this into your first post

This is a starter post, not a finished essay. Rewrite it into your first piece, change the frontmatter above, and use the examples below as a quick reference for how the site handles long-form content.

Write like a document, not a template

Regular Markdown covers most of what a post needs: headings, links, emphasis, lists, quotes, images, and code. The site supplies the typography and spacing.

A good personal site is less about having a content strategy and more about making a reliable place for unfinished curiosity.

For example, a technical post can include highlighted code:

type Signal = {
  source: string;
  frequency: number;
};

export function tune(signal: Signal): string {
  return `${signal.source} @ ${signal.frequency} Hz`;
}

Images keep their context

Add useful alternative text that explains what the image contributes. Keep post-specific images close to the post when they need Astro optimization, or place simple shared assets in public/images.

Topics create their own archive

The topics list in frontmatter powers the topic pages automatically. Use the same spelling for recurring subjects, keep the list focused, and let the taxonomy grow from real posts rather than creating empty categories in advance.

When this reference has done its job, replace the title, summary, date, topics, and body with something only you could write.