Prepare one month of posts, then publish through evidence.

Open the admin area.

Use /admin/ to manage blog posts and the monthly editorial pipeline. Local editing uses Decap local backend. Production publishing requires replacing OWNER/linort-site in public/admin/config.yml with the real GitHub repository and adding the OAuth/auth provider for that repository.

Monthly publishing model.

Create the month's posts at once, set draft: true while writing, assign one clear CTA per post, then switch draft to false only after review. Future publishDate values stay hidden until a rebuild happens on or after that date.

Admin utilities included.

The admin has a blog editor, draft/published filters, practical-gift filtering, media uploads, and a monthly pipeline file for planned posts, status, purpose, target date, and CTA. That gives you a lightweight editorial operating system without adding a database.

Recommended monthly cadence.

Prepare four posts per month: one thesis post, one CLI/terminal guide, one validation artifact, and one command-by-command tutorial. The goal is to educate builders while producing artifacts that narrow the gap between vibe coding and a durable business process.