Notes from the edge

Content lives in Git; the site renders it close to your readers. That keeps editing familiar and deployments simple.

Bulleted ideas

• Cache markdown listings and files so you rarely hit GitHub API limits.
• Search can run in the browser over a cached index—no query per keystroke.
• Drafts stay out of production when draft: true in frontmatter.

Numbered flow

1. Author commits Markdown.
2. Webhook bumps cache version or TTL expires.
3. Next request rebuilds directory listings from GitHub once, then KV serves the hot path.

A blockquote for typography checks. It should read clearly in both light and dark system themes.

Inline media

Side-by-side style is just two images in a row in Markdown:

Short clip (optional)

Comparison table

Approach	Pros	Cons
Git + MD	Versioned, simple	No WYSIWYG
Headless CMS	Editorial UI	Extra service
DB-only content	Dynamic	Heavier to run

Task list

• Ship first version
• Add RSS feed (future)
• Tune cache TTLs per environment

{
  "edge": true,
  "content": "github"
}

---

End of sample post.