Skip to content
ShannonTucker edited this page Feb 15, 2022 · 2 revisions

Details

Based on feedback from stakeholders and subject matter experts, the DECD Design System will have minimal divergence from the existing Canada.ca Design System.

Instead, we will leverage existing components, templates and guidelines as much as possible, while looking for opportunities to…

  1. Alter the designs if required by device support, usability test results or to improve inclusivity
  2. Augment the designs when a Digital Centre requirement or Design System best practice demands
  3. Add new components and templates as required

In all cases, the DECD Design System team will work closely with the Canada.ca Design System stakeholders and caretakers to integrate work back for the benefit of all GoC department.

  • We will continue to develop Figma and React/Tailwind component libraries for the benefit of DECD experience designers and developers, while working to harmonize the Canada.ca and My Service Canada Account user experiences.

  • We will look for opportunities to build upon the existing Canada.ca Design System documentation (in the open) and to share our code as open-source

  • We will work with the cross-departmental group looking to develop a GoC Design System based on the Canada.ca foundation

The benefits of this approach, include:

  • Comprehensive documentation on existing components
  • Extensive usage on Canada.ca and many other GoC websites and experiences
  • Reuse of prior work will reduce effort and schedule
  • Reduced impact of concurrent design
  • Existing design components adhere to governing standards
  • Users moving to and from Canada.ca and other GOC sites using the components should have a very uniform experience
  • Government of Canda brand is easy to understand
  • Already used by CDTS for .Net and Java development components
  • Opportunity to contribute new components back to Canada.ca/GDS for the greater good