blog: move post registry to JSON + add iso_date#75
Merged
Conversation
Convert blogPosts.ts to a thin shim over blogPosts.json so the registry is data (byte-stable, diff-friendly) rather than a TS array literal. Backfill an additive iso_date on all 105 entries (derived from date + year); date/year left unchanged so RSS (feed.xml) and layouts render identically. Build output verified byte-identical site-wide (0 diffs after normalizing build timestamps).
Contributor
|
🚀 Preview deployed to Cloudflare Pages
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Enabling refactor for the blog-admin dashboard (M0). Makes the blog registry editable as data.
What
src/data/blogPosts.tsbecomes a thin shim that importssrc/data/blogPosts.jsonand re-exportsblogPosts, theBlogPostinterface (now with optionaliso_date), andcategories— unchanged public API.blogPosts.jsonwith an additiveiso_date(derived fromdate+year).date/yearare untouched so RSS (feed.xml) and layouts render exactly as before.Why
A JSON registry is byte-stable and diff-friendly, so a management dashboard can do CRUD on posts via atomic commits without rewriting a TS literal.
iso_dategives sane ordering/sorting for tooling.Verification
feed.xml. Only differences were two build-nondeterministic tokens (the nav's live version string, present on every page, and the feed<lastBuildDate>). After normalizing those out: 0 files differ site-wide.npm run check:plainpasses.iso_date, newest-first order preserved.