Repository navigation
openspec: define docs-book-ux-fixes change (proposal, spec, design, tasks) - #85
Merged
Merged
Conversation
Rewrite the capability spec as parseable OpenSpec deltas: each section becomes a '### Requirement:' block with '#### Scenario:' WHEN/THEN entries, splitting the long Mermaid requirement into contrast and theme-independence requirements. Content 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
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.
Lands the OpenSpec definition of the
docs-book-ux-fixeschange, the last artifactmissing for ADR issue #60.
Closes #60
Context
The implementation of #60 already shipped on
docs/documentationsvia PR #61(typography control, ghost buttons, sidebar accordion, Mermaid contrast) and PR #63
(resize reflow, same-page section toggle, How-to chapter placement);
docs/skin/custom.css,docs/skin/custom.jsandCHANGELOG.mdare byte-identical between this branch's historyand
docs/documentations. Only the planning artifacts never landed: PR #62 targeted thewrong base and PR #64 was closed as incorrectly targeted.
What this PR contains
openspec/changes/docs-book-ux-fixes/—proposal.md,design.md,specs/docs-book-theme/spec.md,tasks.md(15/15 tasks checked),.openspec.yamlmain, so the diff touches only the change's OpenSpec files (the previous incarnation draggeddocs/history that lives exclusively ondocs/documentations)### Requirement:+#### Scenario:blocks);openspec validate docs-book-ux-fixespasses with zero errorsVerification
openspec validate docs-book-ux-fixes→Change 'docs-book-ux-fixes is valid'mdbook build docsondocs/documentationsplus the visual checks recorded in the tasks list (3 font steps, both themes)