feat: migrate blog FAQs to reusable MDX accordion
- add Astro MDX support and convert FAQ-bearing posts to MDX - centralize FAQ markup, scoped styling, behavior, and JSON-LD - preserve FAQ content and links across English and Spanish posts - extend blog audits and document the MDX editing workflow - remove obsolete global FAQ styles - ignore Front Matter CMS generated state
This commit is contained in:
@@ -1,5 +1,6 @@
|
||||
# Blog Content Audit
|
||||
|
||||
Checked 65 blog post bodies for layout content duplicated in Markdown.
|
||||
Verified 125 FAQ questions across 19 FAQ-bearing posts.
|
||||
|
||||
No duplicated article headers were detected.
|
||||
No duplicated article headers or invalid MDX FAQ components were detected.
|
||||
|
||||
@@ -31,5 +31,8 @@
|
||||
from all 65 blog Markdown bodies; these elements are rendered by the shared
|
||||
blog-post layout. Updated both extractors and added a blog-content audit to
|
||||
prevent recurrence.
|
||||
- Converted 19 FAQ-bearing blog posts to MDX and restored a reusable
|
||||
`FAQAccordion.astro` component that owns the live-style accordion and
|
||||
matching `FAQPage` JSON-LD.
|
||||
- Added language-qualified content collection IDs to prevent English, Spanish,
|
||||
and Arabic entries with the same slug from overwriting each other.
|
||||
|
||||
@@ -44,6 +44,8 @@ Implemented fidelity work includes:
|
||||
extracted team content as a generic article.
|
||||
- Rebuilt library indexes and blog-post presentation around the live sidebar,
|
||||
article list, byline, featured-image, and counter patterns.
|
||||
- Converted FAQ-bearing posts to MDX and recreated their live-style accordions
|
||||
with a reusable component that emits matching `FAQPage` JSON-LD.
|
||||
- Replaced generic oversized cards, rounded controls, and marketing heroes
|
||||
with live-derived typography, palette, widths, spacing, and compact controls.
|
||||
- Corrected material live/mirror discrepancies found during the pass,
|
||||
@@ -115,7 +117,7 @@ unavailable.
|
||||
- `npm run audit:images`: passed with no missing mapped page banners, section
|
||||
backgrounds, or blog featured images.
|
||||
- `npm run audit:blog`: passed with no article-header content duplicated in
|
||||
blog Markdown bodies.
|
||||
blog content and valid MDX FAQ components for 125 questions across 19 posts.
|
||||
- `npm run generate:sitemap`: passed; generated 97 URLs.
|
||||
- `npm run generate:redirects`: passed.
|
||||
- All migration `.mjs` tools and the sandbox DNS helper pass `node --check`.
|
||||
|
||||
@@ -7,6 +7,8 @@
|
||||
- Shared templates emit canonical, Open Graph, and Twitter card metadata.
|
||||
- Library index layouts emit language-correct canonical URLs.
|
||||
- Blog posts emit article metadata and semantic publication dates.
|
||||
- Blog FAQ components emit `FAQPage` JSON-LD derived from the same MDX item
|
||||
data used for the visible accordion.
|
||||
- `robots.txt` and sitemap generation are included.
|
||||
- The live navigation hierarchy, clean English/Spanish/Arabic routes, and
|
||||
current library listing structure were checked against the public site during
|
||||
@@ -28,4 +30,5 @@
|
||||
- Organization JSON-LD is emitted globally; service-specific schema still
|
||||
requires business review.
|
||||
- Validate social preview images after deployment.
|
||||
- Add page-specific JSON-LD only after business review of the appropriate schema.
|
||||
- Add additional page-specific JSON-LD only after business review of the
|
||||
appropriate schema.
|
||||
|
||||
Reference in New Issue
Block a user