Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[UX Primitives] Split our own primitives from designed components #292

Open
seedy opened this issue Feb 16, 2022 · 0 comments
Open

[UX Primitives] Split our own primitives from designed components #292

seedy opened this issue Feb 16, 2022 · 0 comments
Labels
00-type/task enhancement New feature or request

Comments

@seedy
Copy link
Contributor

seedy commented Feb 16, 2022

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: UnstyledLink has that purpose but is only used internally
  • Button
  • IconButton (could have same primitive as Button)
@seedy seedy added enhancement New feature or request 00-type/task labels Feb 16, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
00-type/task enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant