Line 1: |
Line 1: |
| + | {| style="background: rgb(232, 232, 232); border: 1px solid rgb(136, 136, 136); border-image: none; color: black;" width="100%" cellpadding="2" |
| + | |- |
| + | |[[GC_Design_System_Product_Team|GC Design System Product Team]] |
| + | |} |
| + | {| style="background: rgb(232, 232, 232); border: 1px solid rgb(136, 136, 136); border-image: none; color: black;" width="100%" cellpadding="2" |
| + | |- |
| + | |[[L’équipe_de_produits_du_système_de_conception_du_GC|L’équipe de produits du système de conception du GC]] |
| + | |} |
| + | __NOTOC__ |
| [[fr:Revue de sprint 1 - 29 septembre]] | | [[fr:Revue de sprint 1 - 29 septembre]] |
− |
| |
| == Product: == | | == Product: == |
| Product vision, mission + high level objectives progress overview | | Product vision, mission + high level objectives progress overview |
| * The product team worked to define a shared vision and mission for the design system: | | * The product team worked to define a shared vision and mission for the design system: |
| | | |
− | * <b>Vision</b>
| + | <b>Vision</b> |
− | **For public servants who need to meet evolving digital service delivery standards and the public's expectations, the GC Design System is a solid foundation that increases the quality and efficiency of their work, enables them to build services that are inclusive and provides a framework to ensure reliable task success.
| + | *For public servants who need to meet evolving digital service delivery standards and the public's expectations, the GC Design System is a solid foundation that increases the quality and efficiency of their work, enables them to build services that are inclusive and provides a framework to ensure reliable task success. |
− | * <b>Mission</b>
| + | <b>Mission</b> |
− | ** Driven by modern design, standards and technology best practices, the GC Design System is informed by data and focused on the needs of people. It helps teams deliver a cohesive, accessible and trusted Government of Canada experience.
| + | * Driven by modern design, standards and technology best practices, the GC Design System is informed by data and focused on the needs of people. It helps teams deliver a cohesive, accessible and trusted Government of Canada experience. |
| * Next steps - the team is now working to define: | | * Next steps - the team is now working to define: |
| ** what a GC Design system is | | ** what a GC Design system is |
Line 22: |
Line 30: |
| ==Governance:== | | ==Governance:== |
| Findings from the analytics and user feedback on design.canada.ca | | Findings from the analytics and user feedback on design.canada.ca |
− | *[[Media:Canada.ca design system - Analytics and feedback.pdf | Presentation: Canada.ca design system - analytics and feedback]] | + | *<b>[[Media:Canada.ca design system - Analytics and feedback.pdf | Presentation: Canada.ca design system - analytics and feedback]] </b> |
| **Web analytics (January 1st - Sept 15) and feedback tool (added in June 2021) | | **Web analytics (January 1st - Sept 15) and feedback tool (added in June 2021) |
− | *Highlights:
| + | <b>Highlights: </b> |
− | **Content Style Guide gets the most traffic
| + | *Content Style Guide gets the most traffic |
− | **Templates getting more views than components
| + | *Templates getting more views than components |
− | **Little traffic to French pages (5-10% for most pages)
| + | *Little traffic to French pages (5-10% for most pages) |
− | **Mobile use is low (10-15%)
| + | *Mobile use is low (10-15%) |
− | *Key takeaways:
| + | <b>Key takeaways:</b> |
− | **Canada.ca design system is mostly used by people from web comms community
| + | *Canada.ca design system is mostly used by people from web comms community |
− | **Web comms community is still looking for guidance: templates, guidance on which component to use, clarification
| + | *Web comms community is still looking for guidance: templates, guidance on which component to use, clarification |
| *Hypothesis: | | *Hypothesis: |
| **This is not where developers are generally coming, so we need to understand their needs better if we want to address them | | **This is not where developers are generally coming, so we need to understand their needs better if we want to address them |
| | | |
| ==Guidance: == | | ==Guidance: == |
− | * [[Media:FINAL-7154075 1 Copy of GC Design System October 2021-EN.pdf|Presentation: GC Design system comparative analysis]] | + | * <b>[[Media:FINAL-7154075 1 Copy of GC Design System October 2021-EN.pdf|Presentation: GC Design system comparative analysis]] </b> |
| *Compared 23 design systems based on: | | *Compared 23 design systems based on: |
| **Navigation | | **Navigation |
Line 44: |
Line 52: |
| **Versioning and history of components | | **Versioning and history of components |
| | | |
− | *Highlights:
| + | <b>Highlights: </b> |
− | **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: |
Line 64: |
Line 72: |
| **We found that there is a lot to consume between WET, Canada.ca style guide, policies, etc. | | **We found that there is a lot to consume between WET, Canada.ca style guide, policies, etc. |
| | | |
− | *Next steps:
| + | <b>Next steps:</b> |
| *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 | | *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
| + | *Align the product team regarding standards, values, speaking a common language |
| *Clarify the different meanings of guidance | | *Clarify the different meanings of guidance |