Repository navigation
feat(docs): split the Textarea page into an overview and a page per layer - #67
Merged
alexgrozav merged 1 commit intoOct 22, 2026
Merged
Conversation
…ayer The Textarea page becomes a folder shaped like the Button's: an Overview with a card per layer, and a page each for UI, UX, DX and AX, with that layer's rules and questions. The text moves as it is. Links to the page's own sections now go to the part that holds them. Co-authored-by: multica-agent <github@multica.ai>
🚀 Deploying Preview to Cloudflare 🚀Preview URL: https://textarea-sub-pages-uxf-433-opencomponents.blue-water-0397.workers.dev (commit 1b512f1)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 Textarea page is now a folder shaped like the Button's, so readers get a page per layer rather than one long page. The Overview keeps the intro, At a glance with the scope paragraph and the playground, the Checklist's intro, the reference implementation and the sources, and links each layer from a card. The UI, UX, DX and AX pages hold their sections, then their rules under
## <Layer> Checklist, then their questions. The text moves as it is: agents still read one page at/raw/docs/components/textarea.md, with the same outline, rules and contract as before, and old links like/docs/components/textarea#every-statego on to the right part.Links on the Textarea's own pages to its own sections now point to the part that holds them. Links to other components' sections, and other pages' links into the Textarea, are left for the layer that links the split pages to each other.
Each FAQ item went to the layer it answers:
The live examples went with their sections: the playground on the Overview, four on User Interface and three on User Experience. The Developer Experience and Agentic Experience pages have none.
Checklist
feat(docs): add the focus guideline.pnpm check-typespasses.pnpm dev. (Read on the built site served bywrangler devinstead, with Chrome at 1280px and 375px.)pnpm build, thenpnpm lighthouse, still scores 100 in every category. (No homepage changes.pnpm lighthousepasses the 0.95 budget.)