Feature/changelog engineering - #91
Open
harryjupiter148 wants to merge 3 commits into
Open
Conversation
Contributor
|
@harryjupiter148 , please fix failing ci |
axe-core fails CI on any route with no <h1>. All seven inner pages were using <h2> as their top-level heading. Promoting each to <h1> clears the WCAG page-has-heading-one rule. globals.css updated to cover .section h1 alongside the existing h2 rule so styling is unchanged.
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.
What this changes
Adds a repository-driven
/changelogroute, dynamic slug-based detail pages (/changelog/[slug]), an RSS 2.0 feed (/api/rss), and a markdown-backed content loader (lib/changelog.ts). Changelog entries are written directly as markdown files incontent/changelog/with YAML frontmatter metadata, supporting milestone tagging (e.g.,M1,M2), entry categorisation (post,changelog,postmortem), and interactive milestone filtering. Closes #79Why
Grant programmes require periodic progress reports, and hackathon evaluators seek evidence of sustained, iterative progress rather than isolated commits. Previously, progress and architectural decision records (ADRs) lived exclusively in commit history where external stakeholders rarely look. This system makes shipping release notes and postmortems an integrated part of repo contributions, allowing grant reports and audit trails to be automatically assembled by milestone tag while offering an RSS feed for accountless tracking.
How it was verified
npm run buildcompleted with zero errors and generated all 19 static/dynamic pages).generateStaticParamsverified for all seed entries:0001-attestation-settlement-separation,0002-testnet-fee-measurements, and0003-audit-postmortem).npm run build # Result: ✓ Compiled successfully in 63s, 19/19 pages generated, Exit code 0