Create a package release for our Design System #406
Labels
feature: Architecture
Pertains to project architecture and settings
PBV: dev
all issues for engineering roles (devops, backend, frontend, db)
role: devops
Pertains to cd/ci tasks
role: frontend
Pertains to frontend tasks
size: 13pt+
Must be broken down into smaller issues
Milestone
Overview
As a developer, we should make our system easier to manage. For this ticket, let's properly package our design system so that we can implement version control.
Action Items
This should ideally come into multiple stages, with a one or more PR per stage:
Stage 1
Example:
Stage 2
Stage 3
Example:
Resources/Instructions
Resources
The purpose of this PR is to make the Design System document-able and independently manageable. Right now, one difficulty with the design system is that developers are free to edit it at any time, making it hard to impose or enforce any kind of standard. By separating it out, we can document the standard as well as enforce it via making periodic design releases. This helps us make sure that we can revert to different version of our design system should an update break something critical. This in turn allow us to have conversations on how to have better quality control of the design system.
The text was updated successfully, but these errors were encountered: