Quick test post to confirm the deploy pipeline picks up new content end-to-end. Pushed via Tina, indexed by Tina Cloud, built by Cloudflare Pages, served from CDN. Round-trip should be under a couple of minutes.

Why this exists

Mostly to verify a few things at once:

• The Tina admin actually writes a clean markdown file (no surprise frontmatter rewrites)
• Astro picks up the new entry without a config change
• The build watch path config is doing what I expect — content changes still trigger a deploy

What I’m watching for

1. Frontmatter format. Tina serializes pubDate as an ISO timestamp; Astro’s z.coerce.date() accepts it. Existing posts use 'Apr 28 2026' — both should coexist until the next time I edit them through Tina.
2. Slug generation. Tina derives the slug from the filename, not the title. This file is heres-another-one.md → /blog/heres-another-one/.
3. Index page sort order. New posts should appear at the top of /blog since pubDate is the most recent.

Notes for future me

If a new post doesn’t show up after a deploy, the usual suspects are:

• Content collection cache stale — restart astro dev
• Frontmatter validation failed silently (check the Cloudflare build log)
• Schema drift between content.config.ts and tina/config.ts

Nothing fancy here. Just plumbing. Done. Done2 Done 4. Done 5