Repository navigation
docs: write Overview search titles in title case - #90
Merged
alexgrozav merged 1 commit intoNov 17, 2026
Merged
Conversation
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 component Overviews' search titles now use title case, like the layer pages' titles beside them: "Accessible Button - Guidelines" instead of "Accessible Button - guidelines".
AGENTS.mdandCONTRIBUTING.mdgive the new pattern and say that aseo.titleis in title case, unlike a heading. The example inrawTitle()'s comment and its tests follow.Only the title text changes. An Overview's markdown copy and its
llms.txtlink still use the component's name, "Button".Checklist
feat(docs): add the focus guideline.pnpm check-typespasses.pnpm dev. (Not run: onlyseo.titles changed, which show in the tab and search results, not on the page. I checked the built<title>andog:titleindist/instead.pnpm test,check-reference,check-seoandcheck-mcppass.)pnpm build, thenpnpm lighthouse, still scores 100 in every category. (No homepage changes.)