[UX Primitives] Split our own primitives from designed components
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 41
- Forks
- 16
- Avg merge
- 3d 1h
- Merged PRs (30d)
- 3
Description
Description
For some components, we created our own primitives AND designed them according to our mockups. In the same time, we have other uses for the primitives.
I think it would be a good idea to create 'unstyled" versions of those components, so they can also be reused for said purposes.
I noticed a few places on other projects where we start from scratch, because we don't have the primitive (without the said styled) exported.
Maybe this first improvement could bring a standard for naming/structuring export of those primitives.
Good candidates so far:
Link:UnstyledLinkhas that purpose but is only used internallyButtonIconButton(could have same primitive asButton)
Contributor guide
No contributing guide indexed for this repository
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
Review the existing Link, UnstyledLink, Button, and IconButton components and their exports. Establish the naming and structure for reusable unstyled primitives, then confirm that the proposed candidates can be reused independently of the designed components.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react, typescript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100