Developing products with a design system/component-based approach · Issue #99 · mainmatter/playbook · GitHub
More Web Proxy on the site http://driver.im/
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, it is not 100% clear that a design system is not only a deliverable of the design department (a reusable UI library in pixels).
Should we detail what a design system is on the technical side? What are the important points to bring up that ensure the system is flexible, maintainable, stable, scalable, and successful? What is important in a UI viewer? How to make sure the system is not abandoned?
The text was updated successfully, but these errors were encountered:
Currently, it is not 100% clear that a design system is not only a deliverable of the design department (a reusable UI library in pixels).
Should we detail what a design system is on the technical side? What are the important points to bring up that ensure the system is flexible, maintainable, stable, scalable, and successful? What is important in a UI viewer? How to make sure the system is not abandoned?
The text was updated successfully, but these errors were encountered: