Repository navigation
test: check every split component page like the Button's - #57
Merged
Merged
Conversation
The tests and check-mcp that proved the Button's split now run once per split folder in 3.components/, found from the files, so each component that's split the same way is in the gate without a change to them. The Button's own anchor, #loading and Variants cases stay as they are. Co-authored-by: multica-agent <github@multica.ai>
…o split-tests-uxf-423
🚀 Deploying Preview to Cloudflare 🚀Preview URL: https://split-tests-uxf-423-opencomponents.blue-water-0397.workers.dev (commit 694a15a)This URL reflects your latest Preview deploymentPreview Deployments by commit
|
4 tasks done
alexgrozav
added a commit
that referenced
this pull request
Oct 23, 2026
… layer (#69) ## What changed The other ten component pages now have the shape the Button's got in #54: the Card, Checkbox, Checkbox Group, Dialog, Input, Radio Group, Spinner, Switch, Textarea and Tooltip each become a folder in `content/docs/3.components/`. Each folder holds an Overview and a page per layer: User Interface (UI), User Experience (UX), Developer Experience (DX) and Agentic Experience (AX). The text moves as it is. The only changes are the ones the Button's split made: the cards in place of the intro's list of layers, At a glance starting before the paragraph on examples, the four Checklist links, each part's rules under "UI Checklist" and so on, its questions under its own FAQ, and link targets. Once the Checkbox was a folder, Nuxt Content would have listed Checkbox Group before it, since it sorts by file path and `-` comes before `/`. `app/lib/navigation.ts` keeps the component pages in name order in the sidebar, the header's menu and the links to the previous and next pages. `app/components/UContentSurround.vue` replaces Nuxt UI's to read that order. The tests that covered the Button's split, and the Button-only checks in `scripts/check-mcp.mjs`, now run once for every split component. Links between components go straight to the section's new page. Links from before the split, like `/docs/components/input#sizes`, still land on the right page through the redirect map. In the sidebar and the header's menu, a component's name opens and closes the list of its pages, the Overview and its layers, without navigating, so you pick the page you want. The group still opens on any of its pages and closes once you leave them. Agents see no difference. `/raw/docs/components/<component>.md` and `.yaml`, and the MCP server, serve each component as one page with the outline and contract it has on `main`. The FAQ comes back grouped by layer. A changelog entry announces the change, and `AGENTS.md` and `.github/CONTRIBUTING.md` now say every component page is split like the Button's. It collects these PRs, each reviewed on its own: #56 (component order), #57 (split tests), #58 to #67 (one per component), #68 (links between components, changelog, guides) and #70 (the name opens the group, without navigating). To try it, run `pnpm dev` and open `/docs/components/checkbox`. ## Checklist - [x] The title follows [Conventional Commits](https://www.conventionalcommits.org), as in `feat(docs): add the focus guideline`. - [x] `pnpm check-types` passes. - [x] Docs changes: the pages read well on `pnpm dev`. (Checked on a `pnpm build` served with `wrangler dev`.) - [x] Homepage changes: `pnpm build`, then `pnpm lighthouse`, still scores 100 in every category. (No homepage changes, but the redirect map now covers eleven components and loads on every page, so it ran: 100 in every category on all three runs.) --------- Co-authored-by: multica-agent <github@multica.ai>
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.
What changed
The tests and checks that proved the Button's split now cover every component page split the same way, so each component that moves into a folder of its own is in the gate without a change to these files.
server/lib/raw.test.tsruns its split-page tests once per folder incontent/docs/3.components/that has anindex.md, named for the folder. Each page is one page with its parts joined back in, with the outline every component page has. It has a page per layer, each ending with its rules and then its questions, if it has any. Its.navigation.ymlnames the folder with an icon. Its Overview has no FAQ, a card for each part with that part's description, and a link to each part's rules. Its anchor map sends every section of its parts on to them, and none of the Overview's. The Button's own anchor cases stay as they were.mcp/lib/standard.test.tsreads every split page's rules from its layer pages' tables.mcp/lib/pages.test.tsfinds every split page from each of its parts' paths, with an anchor and as its/rawfile.scripts/check-mcp.mjschecks every page that has parts: each part's path reads the whole page, a part's link with an anchor reads that section, the UX rules hold one of its rules, and the introduction links every part. The Button's#loadingand Variants checks stay.No content, join, redirect map or sidebar changes.
Checklist
feat(docs): add the focus guideline.pnpm check-typespasses.pnpm dev. (No docs changes.)pnpm build, thenpnpm lighthouse, still scores 100 in every category. (No homepage changes.)