@edvisor/product-language
v0.11.107
Published
Edvisor.io product-language components
Keywords
Readme
product-language
This library was generated with Nx.
Storybook Guidelines
Bellow there are some goals to drive our way to build the design system stories with Storybook
The structure on Figma and Storybook needs to stay with the same names (consistency is the key). Please tell us if you detect some structure that aren't following that
Developers from the engineering team shouldn't need to open the code on their editors in order to understand and see how the things is working
- The stories page from each component should be clear with what they have and what they don't have. In that case, use (or add) those information on Changelog (Roadmap)section
Components pages should be small and easy to understand. Don't be afraid to create a lot of pages to same component with their variations
- Display only the props that can change the component behavior/display
Display best practices thinking on developers usage (if the situation required that)
Incrementally, we should have some pages that can render something nearly the mockups world, in order to make easy to figure out the components working together
Foundations Pages
Bellow there are some goals about the Foundations pages
- Explain the guidelines and the fundamentals from a Design Perspective
- Can teach developers people to learn about how the design works
- This kind of pages don't need to show code/how to use
Running unit tests
Run nx test product-language to execute the unit tests via Jest.
