Improve design system concepts schema
Nobody has claimed this yet.
- Dominant language
- MDX
- Stars
- 4.5k
- Forks
- 226
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 4
Description
Following on from #845
Currently design system components have "concepts" and "anatomy". Concepts seems a rather broad term for what could be many different things. For example state pseudo classes (inc custom state ones), any corresponding UI behaviours associated with these pseudo class states, API methods, and attributes could all be "concepts". Is it worth us trying to segregate these a bit?
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
Start by reading issue #845 and reviewing how design-system components currently define “concepts” and “anatomy.” Consider the issue’s examples—state pseudo-classes, UI behaviours, API methods, and attributes—and identify the scope of the proposed schema change. Done requires an agreed separation or decision to retain the current structure.
Written by the indexing model from the issue text.
Assessment
- Domain
- design
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100