Repository navigation
fix(docs): link the split component pages to their new sections - #68
Merged
alexgrozav merged 1 commit intoOct 22, 2026
Merged
Conversation
Links between the ten split components, and the Button's two into the Spinner, now point to the page each section lives on, with targets from readSplitAnchors. A changelog entry announces the splits, and the guides no longer name an unsplit component page. Co-authored-by: multica-agent <github@multica.ai>
🚀 Deploying Preview to Cloudflare 🚀Preview URL: https://link-component-sub-pages-uxf-435-opencomponents.blue-water-0397.workers.dev (commit 221f1b5)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
Now that every component page is split like the Button's, the links between them go straight to the section's new page rather than through the redirect map. That's 33 links: 31 between the ten split components (mostly the Checkbox Group into the Checkbox, and four pages into the Input) and two from the Button into the Spinner. The targets come from the map
readSplitAnchors("content/docs")builds, the same one the redirects use, so the links land where an old link would have. Links to an Overview's own sections, like#checklistand#reference-implementation, stay as they are.A changelog entry,
component-sub-pages.md, tells readers the ten components now each have an Overview and a page per layer, that links from before still work, and that agents still read each one as one page.AGENTS.md,.github/CONTRIBUTING.mdand the comment innuxt.config.tsno longer name3.components/card.mdas an unsplit page, and say every component page is split like the Button's, which stays the model.No guideline text changes, and nothing in
plugins/changed, so the plugin keeps its version.Checklist
feat(docs): add the focus guideline.pnpm check-typespasses.pnpm dev. (Not run: only link targets changed on the pages. Afterpnpm build, all 239 links to a layer page's section in the docs, app, plugin and guides have theiridon the built page.)pnpm build, thenpnpm lighthouse, still scores 100 in every category. (No homepage changes. Ran it anyway: 100 in every category on all three runs.)