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
Component and pattern documentation pages have usage images that are built to a specification that includes aspect ratios, image sizing, file types, margins, background colors, and highlighting techniques:
Callouts
Opacity and boxing
Crops and truncations
Exposed grids
Right now, the means to create the usage images is local to the Carbon team and the Pattern and Asset Library (PAL) teams don't have an easy way to create their own usage images to the same specification.
Enabling the Carbon team and community to build usage images the same way now provides a good north star and prevents a future effort to bring usage images into alignment when consolidating library asset documentation to one website.
Job stories
When documenting how to use an asset, I want to create usage images consistent with the rest of the design system so my team can quickly understand the guidance.
Success measures
A new Sketch kit for production guidelines is available on Sketch Cloud and referenced on Carbon's website
PAL teams are able to use the Sketch team to update the usage images for the assets that they maintain
Summary
Component and pattern documentation pages have usage images that are built to a specification that includes aspect ratios, image sizing, file types, margins, background colors, and highlighting techniques:
Right now, the means to create the usage images is local to the Carbon team and the Pattern and Asset Library (PAL) teams don't have an easy way to create their own usage images to the same specification.
Enabling the Carbon team and community to build usage images the same way now provides a good north star and prevents a future effort to bring usage images into alignment when consolidating library asset documentation to one website.
Job stories
Success measures
Sponsoring team
@jeanservaas
The text was updated successfully, but these errors were encountered: