Search


Purpose

This map converts the completed WET/GCWeb Dependency Inventory and Shared Template Inventory into implementation guidance. It distinguishes direct GCDS replacements from composed patterns, native or custom implementations, and patterns with no current GCDS equivalent.

The map reflects the current GC Design System component catalog as reviewed on 2026-08-26. The implementation phase must pin and test a specific GCDS package version before relying on any component API.

Migration Types

Component Mapping Matrix

The following table maps high-usage shared patterns to implementation targets. Bold text in the first column identifies each current pattern for easier row navigation.

Current Pattern Locations Target GCDS Equivalent Migration Type Risk and Notes Implementation Priority
WET CSS and JavaScript runtime head.njk, base.njk, index.html, 404.html GCDS web components and CSS Shortcuts Direct foundation Pin package versions and preserve a usable pre-upgrade render; remove jQuery only after all WET plugins are replaced Foundation
GCWeb branded header header.njk <gcds-header> Direct Compose related search, language, and navigation components; verify only one banner landmark Shell
Government signature and wordmark assets header.njk, footer.njk, 404.html <gcds-signature> or signature supplied by header/footer Direct Do not duplicate identity elements already rendered by the shell components Shell
Language toggle and custom counterpart URL logic lang.njk, header.njk <gcds-lang-toggle> Composed Preserve toggle, locale, home-page handling, and suppression when a translation is unavailable Shell
Canada.ca search form header.njk <gcds-search> Direct Preserve the search endpoint, query parameter, localized label, and keyboard submission Shell
Canada.ca theme and topic menu loaded by AJAX header.njk <gcds-topic-menu> Direct Confirm the component supplies the required global links before removing data-ajax-replace Shell
Site navigation header.njk <gcds-top-nav> Direct Use for site links, not as a substitute for the Canada.ca theme and topic menu; verify active-page state Shell
Breadcrumb trail breadcrumbs.njk <gcds-breadcrumbs> Direct Preserve hierarchy and pathPrefix; verify the current page is represented according to the component API Shell
GCWeb branded footer footer.njk <gcds-footer> Direct Map contextual links from footer.js without duplicating standard Government of Canada links Shell
WET skip links skipnav.njk, base.njk Header skip-link API or a native skip link Composed The target must become visible on focus and move focus to an existing main-content target Shell
Bootstrap containers and columns base.njk, shared partials, landing pages, standalone pages <gcds-container> and <gcds-grid> Direct Replace layout classes by page family and test text reflow at 200% and 400% zoom Foundation
Date modified region pagedetails.njk <gcds-date-modified> Direct Preserve the localized date and existing Eleventy date source Shared UI
Static warning and information alerts alerts.njk, alert-landingpages.njk, standard-alert.njk, office365Notice.njk <gcds-notice> Direct Select information, success, warning, or danger from message meaning; static notices must not become live alerts Shared UI
Archived sticky and in-view banner archived.njk, archived-text.njk <gcds-notice> plus optional custom sticky behavior Composed No direct replacement for wb-inview or wb-overlay; prefer one persistent notice and avoid obscuring focus or content Shared UI
WET screen-reader-only utility Shared templates, landing pages, content pages, index.html, 404.html <gcds-sr-only> or an equivalent CSS Shortcut Direct Use only where semantic HTML cannot provide the same context; hidden text must remain in the accessibility tree Shared UI
Glyphicons and FontAwesome icons Header, contribute, downloads, roles, alerts, page directory, landing pages <gcds-icon> Direct where icon exists Preserve visible text for file types and external links; decorative icons must be hidden from assistive technology Shared UI
Bootstrap buttons Header, splash page, page directory <gcds-button> Direct Links that navigate remain links; use buttons only for actions Shared UI
GCWeb doormats and service-information lists collectionsMain.njk, about.njk, role-group-sections.njk, updatesMain.njk, bilingual landing pages Native headings and link lists in <gcds-grid> Native/custom GCDS advises against using cards in place of Canada.ca doormats; preserve heading and list relationships Page families
Card-like content previews Page directory card view and any verified preview pattern <gcds-card> in <gcds-grid> Direct when card use criteria fit Do not convert every grouped link into a card; avoid nested interactive controls Page families
Office document navigation office-toc.njk Labelled native navigation list or verified GCDS side navigation Native/custom The current links are peer-document navigation, not a multi-step process; do not map them to tabs or <gcds-stepper> Page families
Download block and file-type icons download.njk Native download link, <gcds-icon>, and GCDS layout components Composed Keep file type and size as text; the icon cannot be the only indicator Page families
Page-directory overlays and clauses lightbox pageList.njk, pageListTable.njk, scope.njk Native inline content or disclosure; <dialog> only for a confirmed modal task No equivalent GCDS has no modal or lightbox component; prefer inline access for filters and long reference content Complex features
Tag filtering and card search pageList.njk GCDS form controls plus custom filtering and result status No equivalent Replace wb-tagfilter; group controls, preserve state, and announce result count and no-results changes politely Complex features
Enhanced directory table pageListTable.njk <gcds-table> plus separately justified custom enhancements Composed Table presentation is direct; filtering, sorting, pagination, result status, and column controls require independent redesign and testing Complex features
WET table-to-chart behavior analytics-chart.njk, src/_scripts/chart.js Native data table plus separately evaluated chart enhancement No equivalent GCDS has no chart component; the table remains authoritative and the chart needs equivalent text and non-colour cues Complex features
WET footnotes Bilingual ICT procurement guides Native reference links, footnotes section, and descriptive return links Native/custom Preserve stable identifiers and bidirectional keyboard navigation; plugin JavaScript is unnecessary Page families
Equal-height plugin office-toc.njk, updatesMain.njk, landing pages <gcds-grid> or native CSS grid Remove Modern grid layout removes the need for equal-height JavaScript Cleanup
WET spacing, visibility, border, and text utilities Shared templates, SCSS, content pages GCDS CSS Shortcuts and design tokens Direct styling Replace by pattern rather than mechanical class substitution; responsive hiding must not remove required information Cleanup
Bootstrap wells and custom page banner base.njk, home.njk, banner.scss, content callouts Native semantic content with GCDS CSS Shortcuts; <gcds-notice> only for actual notices Native/custom A visual box is not automatically a notice; preserve one page-level heading and avoid component wrapping for prose Cleanup
Inline WET classes in Markdown content src/pages/**/*.md Native HTML plus GCDS CSS Shortcuts where presentation remains necessary Native/custom Follow Decision 001; remove obsolete classes without changing content semantics or bilingual parity Cleanup
Splash image randomizer index.html Static presentation or separately justified custom script No equivalent Prefer removal; if retained, ensure full operation without JavaScript and prevent layout shift Standalone pages
Standalone splash and not-found shells index.html, 404.html Composed GCDS signature, container, grid, link, and footer patterns Composed These pages bypass Eleventy layouts and need independent bilingual, keyboard, and no-JavaScript validation Standalone pages

Explicit Gaps and Redesign Inputs

The following WET behaviors have no current one-to-one GCDS replacement:

These gaps are evaluated in the No-Direct-Replacement Analysis for issue #774. They must not be implemented through speculative custom-element names.

Implementation Guardrails

Completion Assessment

Page details

Date modified: