Anatomy Schema "part" names?
Nobody has claimed this yet.
- Dominant language
- MDX
- Stars
- 4.5k
- Forks
- 226
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 4
Description
Currently the revised design system anatomy schema looks something like:
Part was chosen as it should be generic enough to be usable by both WebComponent and Browser impl design system data.
This issue is mainly can anyone think of a better name to be generic for all the different paradigms?
(Note: legacyPart is designed to convey the prefixed pseudo elements in browsers)
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 reviewing the revised design system anatomy schema shown in the issue, including the proposed part and legacyPart names. Compare terminology across the WebComponent and browser paradigms, then determine whether the project can agree on a more generic name; done means a documented naming decision.
Written by the indexing model from the issue text.
Assessment
- Domain
- design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100