Large Design systems like dialect DS have really big set of styles. To be able to access the token values for that type of Design System requires to optimize the space in the Style Book editor so that multiple groups of types can be shown.
The goal of this story is to enhance the style book editor in order to support sub-group of styles.
When editing a stylebook
Then the styles are grouped using an additional group of level the first group appearing in the sidebar via icons.
- Color system
- Does this feature modify something already existing in the product?
- Why is the change proposed?
And example would be:
Does this feature modify something already existing in the product?
Yes, it removes the section component and replaces it with the container component. Existing section components should be replaced with two containers. One with fluid width, and an inner one with fixed width.
Why is the change proposed?
** Section component is more rigid, the container is more flexible allowing more use cases.
During or after the kickoff, the developer would fill a third section:
- Is an upgrade needed?
In this section they would define the steps needed for the upgrade if necessary.
Some example would be:
Is an upgrade needed?
1: We have to create an upgrade process because the properties of the section won’t be compatible with the new container component.
: No upgrade process needed since when reading the properties of the section we will swap it with the new one.
: Nothing to be done, this is already backwards compatible