chore(#3769): Migrate design system guidelines from the MCP into docs site#3771
Open
chore(#3769): Migrate design system guidelines from the MCP into docs site#3771
Conversation
Spark450
reviewed
Apr 10, 2026
Collaborator
Spark450
left a comment
Spark450
left a comment
There was a problem hiding this comment.
Just a few comments and suggestions.
| tags: | ||
| - user-types | ||
| - citizen | ||
| - worker |
Collaborator
There was a problem hiding this comment.
I know when I was reviewing the "workspace" docs I pushed to have this term changed to "service delivery worker". Should we align the language in this document as well?
| @@ -0,0 +1,15 @@ | |||
| --- | |||
| id: linkbutton-vs-link | |||
Collaborator
There was a problem hiding this comment.
Should we remove this one, since we are going to undocument the link-button?
| --- | ||
| id: pagination-links-only-mobile | ||
| type: tip | ||
| description: Use variant='links-only' for a simpler mobile-friendly pagination with just previous and next links. |
Collaborator
There was a problem hiding this comment.
I think right now we have buttons instead of links in the pagination control, should we change the description to say "...previous and next buttons"
| --- | ||
| id: picking-a-date-component | ||
| type: tip | ||
| description: "DatePicker handles most date inputs. Use type='input' (a dropdown for month and text inputs for day and year) for known dates like birthdays, far in the past or far in the future. Use type='calendar' (a popup calendar) for dates closer to real time when the user is picking from available days, like booking or scheduling." |
Collaborator
There was a problem hiding this comment.
should "for dates closer to real time" instead be: "for dates closer to the current day"
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
2 participants
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.
Closes #3769
The MCP repo has design system guidelines that should be in the docs site. This PR migrates them into the docs site content collections so the per-component ones start showing up on component pages as do's and don'ts right away, and we have a single source of truth to maintain.
What's in this PR
foundations/content collection (schema inconfig.ts, documented inARCHITECTURE.md) for higher-level guidelinesradio-groupinstead ofradioNotes