Repository navigation
Review follow-up 11: spec page composition (relations and features in columns, a facts and revisions panel beside them) - #71
Merged
Conversation
…evisions in a panel beside them The spec pages read as one long list. Relations and features now take the wide column and pack into columns; a sticky panel beside them holds the figures (count-up, M3) and the revision timeline (rail draw-in, M13). A spec with no recorded features says so in the panel instead of showing a zero. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01HjyoQhmK85j5jqTFVYFDEh
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01HjyoQhmK85j5jqTFVYFDEh
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01HjyoQhmK85j5jqTFVYFDEh
jbspeakr
force-pushed
the
claude/project-thread-ehsdpe
branch
from
October 22, 2026 21:13
63ce693 to
ca4c82f
Compare
CI's axe run caught the current-revision chip mid-fade on the tinted panel, below the contrast threshold. The rail still draws in (M13); the entries no longer fade. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01HjyoQhmK85j5jqTFVYFDEh
Generated by the screenshots workflow for #71.
3 tasks done
Resolves the motion catalogue conflict: M12 takes main's wording (the count of checks appears last), M13 keeps the spec page revisions row. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01HjyoQhmK85j5jqTFVYFDEh
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
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.
Requested by Jan · project thread
What this changes
Review follow-up 11: the composition of the 41 spec pages. Before, each page was one long list: revisions, then relations, then features. This PR builds on #69, which is merged, and keeps its drawing in the head.
Two columns under the head. Relations and features take the wide column. A panel beside them holds the page's figures (revisions, relations and features, counting up with
Facts.astro, M3) and the revision timeline (its line draws in, M13). On wide screens the panel stays in view as the reader scrolls, like the panel on a breach page. Below 60rem the panel comes after the relations.Relations in columns. The relation groups pack into columns (
columns: 19rem), so a long group leaves no gap next to a short one. A group heading is now only the verb phrase ("Builds on", "Is built on by"), because the page title already names the spec. The Source link follows its note instead of taking its own line.Features by topic. Only MCP Authorization defines features so far. They are grouped by topic (Discovery, Registration and so on), with the same column packing. A thin bar in the level inks shows how many features are MUST, SHOULD and MAY, and the counts are written out beside it, so the bar does not rely on colour alone.
No zero for missing data. The other 40 pages have no recorded features. Their panel says that in one sentence. It does not show "Features 0" or an empty section, because
unknownis notunsupported.Smaller changes. The withdrawn or expired notice moves into the main column, in smaller type.
docs/design.mdand the accessibility statement add the spec page to M3 and M13.tasks.mdgets R-11.Page height at 1440 px: MCP Authorization drops from 5,316 to 3,529 px, Token Exchange from 2,021 to 1,526 px, and WIMSE S2S from 2,124 to 1,643 px. On phones everything stacks in one column, so the pages are only slightly shorter.
Screenshots
These are from
astro previewwith reduced motion, so the animations are in their end state.mcp-authorization, desktop-lightmcp-authorization, desktop-darkrfc8693, desktop-lightrfc8693, desktop-darkwimse-s2s, desktop-lightwimse-s2s, desktop-darkrfc8693, phonewimse-s2s, phonemcp-authorization, phoneThe screenshots were committed once for stable URLs and removed in the next commit, so the squashed diff has no images.
Code checklist
pnpm checkpasses, and the enforced budgets pass. The page adds no JavaScript beyond the existing count-up script inFacts.astro.spec-page.spec.tsgets two new tests: the panel sits beside the main column on wide screens and after it on phones, and a spec with no features shows the sentence and no zero. The existing FR-008 and FR-014 tests pass unchanged, and so does axe. Thespecbaseline is meant to change, so this PR needs therefresh-screenshotslabel. Thestandardsphone baselines also fail locally, but they fail on main too with this container's Chromium.🤖 Generated with Claude Code
https://claude.ai/code/session_01HjyoQhmK85j5jqTFVYFDEh