This sitePostOct 3, 20261 min read

Part 1: Choosing the stack

[One sentence on what this part covers and what the reader will take away.]

This is a sample post. It shows every element the design supports, so keep it as a reference until your first real post is written, then delete it or set draft: true in the frontmatter.

Section headings look like this

Body text goes here. Inline references to services or settings look like setting-name so they stand apart from the prose.

# Code blocks are highlighted with the Nord theme.
resource "example_bucket" "site" {
  name          = "my-blog"
  force_destroy = false
}

Follow a code block with a paragraph on what the code does and why it is written this way.

A placeholder figure

FIG. 1 Put a caption in italics on the line after an image.

What broke

A blockquote that starts with a bold label becomes a callout. Use it for the thing that went wrong, how you noticed, and the fix. These notes are the part readers cannot get from the official docs.

  • A list item
  • Another, with a link

Close with what this part established and what the next part picks up.