Get startedPatternsComponentsStylesContentSupport
Select your development framework to see all code in your development languages. You can change this in the top right of the screen.
Start with the design systemUX DesignersOverviewSetupVerify a bugVS CodeTechnologiesSupported BrowsersVersion update guideQA testingContributeSupportRoadmapUser experience guidelines

Roadmap

A high level summary of the work the design system team plans to complete in 2024. For more information on the latest releases, visit the release notes

Please note the roadmap is subject to changes as we learn more information. We will communicate any updates on the direction of the design system so that product teams can align, prepare, and strategize their work as applicable.

See our GitHub design system backlog for more details on our priorities and day-to-day activities.

Now

Work that is currently in progress.

Citizen-facing form documentation and examples:

  • Objective: To simplify the design and development process by offering predefined page layouts and comprehensive guidelines on the structure and workflow of citizen-facing forms.
  • Benefit: Accelerates delivery, ensures consistency, and maintains high quality across projects.

Angular library wrappers:

  • Objective: To streamline the integration of our components with Angular, enhancing natural development flows and real-time error checking.
  • Benefit: Increases efficiency and reduces development time, enabling Angular developers to utilize design system components more effectively.

Next

Work that we have a clear definition around, discovery is well underway, or we have moved to the design phase.

Sample citizen-facing form:

  • Objective: To create an implementation of a citizen-facing form through an end-to-end sample service that integrates all components as they would appear in actual use.
  • Benefit: Provides a practical example to facilitate the adoption of the citizen-facing form pattern.

Design documentation enhancement:

  • Objective: To centralize design resources by migrating design and usage guidelines from Figma to our design system website.
  • Benefit: Improves accessibility of documentation for teams and allows for the refinement of content based on feedback from earlier iterations.

Future

Work that is currently in the early phases of discovery and may see substantial changes as the work becomes more defined.

Continued focus on patterns:

Patterns will help drive consistency and quality across digital services. They also allow teams to get to working software more quickly, leaving more time for content design, user and stakeholder engagement, and testing.

Complex form pattern:

  • Definition: For frequent or expert users, this pattern emphasizes speed and flexibility, streamlining repeated form interactions.
  • Context: Ideal for scenarios where efficiency and speed are prioritized over clarity and error prevention.

Case management patterns:

  • Definition: To support professional users in managing, reviewing, and processing cases within work contexts.
  • Context: Used in services where cases are created, reviewed, actioned, and processed, supporting "case" workflows.
Join design system drop in hours to get feedback on your service, propose new components or patterns, suggest changes to existing resources, ask questions, and give feedback to the design system. These sessions are for Government of Alberta product teams.
Book time in drop in hours
Get startedPatternsComponentsStylesContentSubmit an issue#design-system-supportContribute to the design systemGive feedbackRelease notes