You don't need a CMS, a database, or a weekend of setup. A practical checklist for adding a blog to any project — and the decisions that actually matter.
Journal / updates / demos
Writing in the same register as the product.
Product notes, implementation details, and interactive demos from the Yamblog codebase, presented inside the same editorial shell as the home page.
Release notes, how-tos, and experiments.
Each entry keeps the same typography, spacing, and material treatment as the landing page instead of falling back to a separate blog theme.
A landing page explains the pitch once. A blog compounds. The concrete, unsentimental case for shipping a blog next to your product.
From empty Astro project to a typed markdown blog with listing, post pages, RSS, and a sitemap — using @yamblog/astro and about forty lines of code.
Skip the headless CMS subscription. Markdown files in your repo, typed queries in the App Router, SEO metadata, RSS, sitemap, and OG images — deployed with git push.
Search engines aren't the only readers anymore. How to structure a blog so AI assistants can find it, cite it, and even help write it.
Why I built Yamblog, why I open sourced it, and why blogs still matter even in the era of vibe-coded SaaS apps.