Add Markdown blog and FAQ content collections

docs/content-model.md

@@ -6,10 +6,21 @@ whether a physical-address map is displayed. Shared Astro components render
 that data without a per-site code fork.
 
 Current reusable primitives include the base SEO layout, header/footer,
-full-page hero, section heading, CTA band, review cards, and optional location
-map. The optional `faq` array provides accessible, static question/answer
-accordions and stays empty until approved content exists. A real logo can be provided as `/images/<safe-name>.svg` or image asset;
-until then the configured short mark and shared favicon are used.
+full-page hero, section heading, CTA band, review cards, Markdown-backed FAQ
+accordions, and an optional location map. A real logo can be provided as
+`/images/<safe-name>.svg` or image asset; until then the configured short mark
+and shared favicon are used.
+
+Phase 6 adds two validated Markdown collections:
+
+- `sites/blog/content/posts/*.md` produces the journal listing and individual
+  `/posts/<slug>/` pages on `blog.3031023.xyz`.
+- `sites/www/content/faq/*.md` produces the FAQ section on the primary-site
+  homepage.
+
+Both collections require frontmatter and support `draft: true`. Draft entries
+are excluded from the rendered pages and sitemap. This is a Git-backed pilot;
+it does not add a CMS or client-editing access.
 
 Images must live under `public/images/`, be referenced with descriptive alt
 text where rendered, and remain at or below the 500 KiB pilot limit. The build