8000 Developing products with a design system/component-based approach · Issue #99 · mainmatter/playbook · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Developing products with a design system/component-based approach #99

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

Open
marhigh opened this issue Jul 24, 2020 · 1 comment
Open

Comments

@marhigh
Copy link
Contributor
marhigh commented Jul 24, 2020

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?

@marcoow
Copy link
Member
marcoow commented Jul 27, 2020

Yes, those are all good points. Do you have any concrete guidelines in mind and could prepare a PR?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants
0