Publish CMS foundation + 2025–2026 events/content (excludes MSS 2026) #18
Loading…
Reference in New Issue
No description provided.
Delete Branch "release/publish-cms-content"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Replace the hand-maintained ARTICLE_DATES registry as the source of truth with dates read from content/ front-matter, so publishing a post via the CMS needs no manual registry edit (plan R4). - tools/content_index.py: load_dates() reads content/ front-matter into {source_folder/slug: {published|modified: iso}}. Standalone (os+yaml), no import cycle with seo_inject. - tools/seo_inject.py: ARTICLE_DATES is now {**static_fallback, **content_dates}; content wins. The static table is kept only as a fallback for entries not present in content/. - migration now preserves the published-vs-modified distinction (date_type), so the switch is byte-identical: content-derived dates equal the old static table exactly (17/17, incl. the one 'modified'). Verified: full `seo_inject --all --sitemap` + build_listings + build_botlinks run produces ZERO changes to any site page. build_content --check still reproduces all 51 pages. build_botlinks.py needs no change (it scrapes built pages, which are a pure function of content/). Listings get content-driven dates for free via seo_inject.ARTICLE_DATES. tools/tests/test_content_index.py: 5 tests (dates == legacy registry, merged registry unchanged, published/modified distinction, events key on projects/<slug>, one ISO date per entry). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>Regenerate assistant/index-{en,mk,si}.json to reflect real event photos and Latinized titles. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>