You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Originally posted by andresgnlez February 14, 2023 Discussion started by @mbarrenechea
Radix UI provides many components out of the box we need in our daily work. It would replace many of our components, like Avatar, Select, RadioGroup, Modal... Meaning less maintenance on our side for these components.
I think it is also a good chance to really scaffold the project at design-level: it would provide a way to really quick way to kick off building pages without touching basic components (further than colors/size settings) and standardize the behavior: we can compromise to develop something really quick following Radix standards, out of that, it would require additional efforts and so more hours/days on our end.
Discussed in #120
Originally posted by andresgnlez February 14, 2023
Discussion started by @mbarrenechea
Radix UI provides many components out of the box we need in our daily work. It would replace many of our components, like
Avatar
,Select
,RadioGroup
,Modal
... Meaning less maintenance on our side for these components.I think it is also a good chance to really scaffold the project at design-level: it would provide a way to really quick way to kick off building pages without touching basic components (further than colors/size settings) and standardize the behavior: we can compromise to develop something really quick following Radix standards, out of that, it would require additional efforts and so more hours/days on our end.
Thoughts? Concerns?
About Radix UI
This issue tracks the migration from the native components we have to RadixUI whenever possible. The migration must:
The text was updated successfully, but these errors were encountered: