Repository navigation
Release v1.3.1: consistent reference layouts and mobile reading - #24
Merged
Merged
Conversation
12 of 15 tasks
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
1 participant
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.
Reference pages had inconsistent reading widths, headings detached from their body columns, and tables that were difficult to scan on phones. Seven views now share one document layout, with aligned headings, a 42rem reading column, sticky desktop contents and native collapsible mobile navigation.
The specification presents the decision procedure as numbered questions, keeps mapping candidates readable on small screens, and provides labelled examples with copy controls. English references and code keep their direction inside RTL pages. Project status is shorter and groups scope, implementation evidence, standards discussion and review records.
This patch preserves classification criteria, decision branches and pending review status. Package, vocabulary and citation versions are aligned at 1.3.1.
Validation:
npm run verify(352 pages, 22 locales and schema/data checks);npm run test:server --prefix mcp; Chrome checks for responsive layouts, keyboard use, both themes, RTL, all 32 wizard paths, no JavaScript and automated WCAG A/AA checks. The nine document routes additionally check heading alignment and mobile contents controls. Desktop, mobile, table, code and gallery screenshots were visually inspected.