Improve design system anatomy JSON Schema
Nobody has claimed this yet.
- Dominant language
- MDX
- Stars
- 4.5k
- Forks
- 226
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 4
Description
Currently the anatomy that can be defined for a component in a design system is rather limited. Just an array of names with a description.
It's also displayed rather simply
It would be good to be able to represent the structure in an anatomy like we can in our anatomy proposals. It would also be good to display the anatomies in a way more akin to the concepts where the various design systems have their anatomies displayed and labelled with where the anatomy comes from.
This would make it far easier to turn these anatomies into a proposal with confidence that we cover X% of design systems.
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
The issue does not name files or tests; start by reviewing the current anatomy JSON Schema and the anatomy proposals it references. Compare the existing anatomy display with the concepts display, then define completion as supporting richer anatomy structure and showing each anatomy with its source design system clearly labelled.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- json
- Domain
- design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100