This repository was archived by the owner on Oct 23, 2026. It is now read-only.
Repository navigation
Give the roadmap a title, and one heading level per section - #17
Merged
Merged
Conversation
The page had two h1s — "From a description to a specification" and, halfway down, "The tracked work" — and no heading anywhere that said "Roadmap". It read as two documents stapled together, and the pivot between them arrived without warning. Lead with "# Roadmap" and a lede that states the page is in two halves: the shape, which is the argument, and the tracked work, which is the generated issue list. Demote both old h1s to h2 and their children to h3, so the outline matches every sibling page. No Liquid logic changed. The where_exp filters stay split one comparison each, for the Jekyll 3.10 that Pages pins. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
The roadmap page was confusing to land on, and the missing title was only part of it.
It carried two
<h1>s — "From a description to a specification" and, halfway down, "The tracked work" — and no heading anywhere that said "Roadmap". It read as two documents stapled together, and the pivot from the argument to the generated issue list arrived without warning. Every sibling page (# Governance,# Versioning,# Contribute) leads with a single h1 naming the page; roadmap was the odd one out.What changed
# Roadmap, plus a short lede saying the page is in two halves — the shape (the four workstreams and the governance problem under them, written as an argument) and the tracked work (the live issue list generated from this repo).Ready to implement/Rough consensus/Under discussion/Raised/Parked/Donegroup headings.Rendered outline:
On the Jekyll 3.10 trap
No Liquid logic changed. The
where_expfilters stay split one comparison each, for the Jekyll 3.10 that GitHub Pages pins — the thing #16 just fixed. The only Liquid line touched is the group heading,##→###on the{% case g %}line.Built locally and checked the rendered
_site/roadmap/index.htmloutline. Local Jekyll is 4.4.1, so that is not by itself proof the Pages build passes — but nothing here is in the 3-vs-4 danger zone, and CI now builds the way Pages does.Content-only. No layout, config, or data changes.
🤖 Generated with Claude Code