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
Currently every new person working on the Hypertrace UI codebase has to go through the components source code to figure out which UI components are available and how to use them. This still doesn't provide a visual cue on what the different variations of the components look like, for example, all the different variations of ht-button available.
Proposal
Setup Storybook so we can have a quick reference of all the shared UI components available in the hypertrace-ui repo.
Questions to address (if any)
As an alternative, maybe we can add a link to the Figma designs so we can get an overview of all the UI components present in the repository. This would still need the devs to deep dive into code to understand usage but at least we'll be able to quickly go through which UI components are available and which ones do we need to create if needed.
The text was updated successfully, but these errors were encountered:
Use Case
Currently every new person working on the Hypertrace UI codebase has to go through the components source code to figure out which UI components are available and how to use them. This still doesn't provide a visual cue on what the different variations of the components look like, for example, all the different variations of
ht-button
available.Proposal
Setup Storybook so we can have a quick reference of all the shared UI components available in the hypertrace-ui repo.
Questions to address (if any)
As an alternative, maybe we can add a link to the Figma designs so we can get an overview of all the UI components present in the repository. This would still need the devs to deep dive into code to understand usage but at least we'll be able to quickly go through which UI components are available and which ones do we need to create if needed.
The text was updated successfully, but these errors were encountered: