Skip to content
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

Code-based design system #3612

Open
4 tasks
allly-b opened this issue Mar 5, 2025 · 1 comment
Open
4 tasks

Code-based design system #3612

allly-b opened this issue Mar 5, 2025 · 1 comment
Labels
design-consult Used when a dev ticket needs limited design consultation dev issue is for the dev team

Comments

@allly-b
Copy link
Contributor

allly-b commented Mar 5, 2025

Issue description

Designers want a design system, like Storybook, so that they don't have to manually create key components in figma and constantly update them when there are changes made in the code or other tickets. The manual process right now leaves room for error and for things becoming out of sync on stable.

Furthermore, for components like tables, there are a lot of different "states" (pagination, sort, filtering, eye/gear icon on rows, etc) that would be far too time consuming to mock up in figma for every possible state combination. This means a designer has to to go to a sandbox to see what is the current of components like tables. Even then some items, such as the eye/gear icon, are dependent on the object state and the users permissions, so just because a designer checks a sandbox they may miss some states because they don't check every permission/object combination (this would be so tedious!).

Our goal is to help with the quality of life for designers by providing a Proof of concept for a design system via code that can be viewable on stable. This will require design and dev to work together, using a single component as an example. By the end of this, the POC should meet the needs of design enough that for this single component they do not need to look at figma as the source of truth.

suggestions of how to work

Acceptance criteria

  • Requirements for a MVP design system are determined
  • a single component is agreed upon by dev & design
  • work is planned
  • work is complete and POC is usable by design

Additional context

This Renewal Pod doc is an awesome example of tracking and communicating work

Notes on ticket creation:

  • If possible, add any tickets as a sub-issue of this ticket. Most likely that will only apply to bundles since other tickets already have parents
  • Label your tickets with dev and/or design and also design-system

Links to other issues

No response

@allly-b allly-b added design issue is for the design team dev issue is for the dev team labels Mar 5, 2025
@allly-b
Copy link
Contributor Author

allly-b commented Mar 5, 2025

Added this to leads discussion if we have time, otherwise it will go to refinement

@allly-b allly-b changed the title Code based Design system Code-based design system Mar 5, 2025
@allly-b allly-b added design-consult Used when a dev ticket needs limited design consultation and removed design issue is for the design team labels Mar 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
design-consult Used when a dev ticket needs limited design consultation dev issue is for the dev team
Projects
Status: 👶 New
Development

No branches or pull requests

1 participant