1,123
edits
Changes
Jump to navigation
Jump to search
Line 59:
Line 59: − + − + − + − + − + − + + + + + + + + + + − Visual foundations guidance: The design system needs a separate “Foundations” section for core visual and brand elements+ − Component guidance: Component guidance should have some content guidance specific to that component. There are many ways to present guidance for developers and designers. Having 2 separate tabs is an option, but not the only option. + − Component history and versioning: There is an opportunity to figure out the best way of conveying changes, versioning, how to upgrade+ − − − − Guidance for users revolves around four sections: − awareness of the digital policy framework − design system guidance − navigating and using the design system − selecting and applying the right tokens and components for the job − − − − − Next steps: − Understand how design decisions are captured at a process level with the goal being to make the design system the trusted source of truth for design system decisions − Align the product team regarding standards, values, speaking a common language − Clarify the different meanings of guidance + + + +
Sprint Review 1 September 29 - Revue de sprint 1 29 septembre (view source)
Revision as of 14:08, 26 October 2021
, 14:08, 26 October 2021→Guidance:
**Versioning and history of components
**Versioning and history of components
Highlights:
*Highlights:
All of them have navigation between elements within a section
**All of them have navigation between elements within a section
11/23 have both top and left navigation
**11/23 have both top and left navigation
Takeaways:
*Takeaways:
Navigation: Making the design system a separate product, with internal navigation, is the common practice
**Navigation: Making the design system a separate product, with internal navigation, is the common practice
Content guidance: The “overarching”, non-component-specific guidance from the Canada.ca Content Style Guide should be in a separate section, within the design system
**Content guidance: The “overarching”, non-component-specific guidance from the Canada.ca Content Style Guide should be in a separate section, within the design system
**Visual foundations guidance: The design system needs a separate “Foundations” section for core visual and brand elements
**Component guidance: Component guidance should have some content guidance specific to that component. There are many ways to present guidance for developers and designers. Having 2 separate tabs is an option, but not the only option.
**Component history and versioning: There is an opportunity to figure out the best way of conveying changes, versioning, how to upgrade
*Guidance for users revolves around four sections:
**awareness of the digital policy framework
**design system guidance
**navigating and using the design system
**selecting and applying the right tokens and components for the job
*Tackling the design system guidance:
**We did an inventory of existing guidance for review and analysis
**We found that there is a lot to consume between WET, Canada.ca style guide, policies, etc.
Tackling the design system guidance:
We did an inventory of existing guidance for review and analysis
We found that there is a lot to consume between WET, Canada.ca style guide, policies, etc.
*Next steps:
*Understand how design decisions are captured at a process level with the goal being to make the design system the trusted source of truth for design system decisions
**Align the product team regarding standards, values, speaking a common language
*Clarify the different meanings of guidance
