Design: Standard page templates

[adorayi]

Standard web page with header, footer, grid and whatever else is needed.

Acceptance criteria

• [x] Template has header
• [x] Template has footer
• [x] Template has a body section that aligns with grid
• [x] Template grows to fill content
• [x] Layout with single column
• [x] Layout with side nav (won't do)
• [x] Mobile variant of all versions

Done when

• [x] EN template is marked ready for dev
• [x] FR template is ready for merge
• [x] A standard process for designing templates is created and shared

Deliverables

• [x] EN template (opens in Figma)
• [x] FR template (opens in Figma)

Dev impact

Yes - Needs HTML equivalent (ticket)

W.I.P.

Basic Page (opens in Figma)

[adorayi]

Template for the dental demo is available and should be used as a starting point.

[adorayi]

Since the search can be toggled on/off, we don't need to include different versions showing that.

[daine]

In the current Acceptance Criteria, there is an item for "Version with side nav" however upon discussion at dev/design sync today it seems it's something that still needs to be looked into. Could we add "Decide if we're proceeding with a version with a side nav" to the "Definition of done", so the devs know during handoff if it exists or not? TIA!

[daine]

Here is the working document on the proposed naming conventions for the standard page templates: https://docs.google.com/document/d/1q4v397adKEHtWgDWUO3PG3jUl62D9RXMyThRASiHwEU/edit#heading=h.cp3wko3y7gcr

It also contains a mapping of existing templates from the source, to our proposed implementation.

[realdylanzheng]

@adorayi The templates rely on a spacing component (concept only) to help designers conveniently set varying space values between sections in a template. Currently we don't have a suitable or complete version of this, requesting that we prioritize to formally create one. Zenhub ticket cc: @nmakuch