Writing Guides in Markdown

Every guide is a single Markdown file in src/content/guides/. The filename becomes the URL slug.

Frontmatter

---
title: "My Guide"
description: "One-line summary used in lists and search."
pubDate: 2026-07-22
updatedDate: 2026-07-23   # optional
tags: ["nginx", "security"]
draft: false              # drafts are excluded from the build
---

Body

Use standard Markdown. Code fences get syntax highlighting automatically:

npm run build

Tags

Tags are free-form strings. Reuse existing tags when possible so the tag pages stay useful — check the homepage chips before inventing a new one.

Drafts

Set draft: true to keep a file in the repo without publishing it. The build skips drafts entirely.