A design system, component library for the web?
Nobody has claimed this yet.
- Dominant language
- MDX
- Stars
- 4.5k
- Forks
- 226
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 4
Description
I'll paste in the summary here from a kickoff meeting we had with @bradfrost:
Hey everyone, as an FYI a few of us met with Brad Frost regarding a global design system based on his post here. To avoid having too many non-open meetings we decided to spin up a channel to try and iterate async on key questions.
- Should this be a design system only and not include a component library?
- If we started a component library what key components would we start with?
- How do we get the right people involved to ensure that it makes progress but also has the necessary rigor to ensure people that adopt it are getting the key goals from this.
This issue to focus on the first topic as the other two follow after that. I'll ping in the discord channel about this to try and centralize the discussion here as well.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Read the kickoff summary and the linked Brad Frost post first, then review the discussion in this issue and the referenced Discord channel. Done means reaching and recording a decision on whether the project should pursue a design system only or include a component library; no files or tests are identified.
Written by the indexing model from the issue text.
Assessment
- Domain
- design, frontend, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100