Add Markdown blog and FAQ content collections

This commit is contained in:
Kevin
2026-09-02 10:25:49 -04:00
parent e45bbe4111
commit 78cfe0cc71
20 changed files with 176 additions and 27 deletions
+6 -5
View File
@@ -11,9 +11,9 @@ Cloudflare Pages site remains the rollback target while this branch is tested.
- `src/` contains shared Astro presentation code.
- `schemas/` and `fixtures/` provide the Phase 1 JSON contract proof.
The blog is static JSON in this phase. Markdown content, CMS workflows, public
sign-up changes, n8n changes, and onboarding-worker changes are deliberately
out of scope.
Blog posts and primary-site FAQs are now static Markdown collections with
validated frontmatter and draft filtering. CMS workflows, public sign-up
changes, n8n changes, and onboarding-worker changes remain out of scope.
## Local checks
@@ -33,8 +33,9 @@ routes, account IDs, or secrets.
## Preview deployment
The Gitea workflow deploys only a non-production Worker from the pilot branch:
`3031023-xyz-www-preview` by default, or the manually selected `blog` site.
The Gitea workflows deploy scoped non-production Workers from the pilot and
Markdown-test branches: `3031023-xyz-www-preview` for primary-site changes and
`3031023-xyz-blog-preview` for blog changes.
It uses the existing `CF_API_TOKEN` and `CF_ACCOUNT_ID`. The token retains the
Pages permissions needed for the `main` rollback target and now also permits
the non-production Worker preview deployment.