tech: build out consolidated prototype

[htmlandbacon]

What

Turn the revisions prototype into a separate data driven prototype.

Why

Current a lot of the structure of the prototype is repeated, we should make this a data driven approach to align with the main site, utilising layouts, templates, markdown and macros.

Done when

Stage 1 - templates

• start new repo
• • Build out a section of single depth pages (component)
• • Build out a section of multiple depth pages (pattern)
• • Build out a collection view
• Add markdown render function
• Add additional set of templates to represent each section
• Create a macro to represent top level navigation (v2 - link needed)

Stage 2 - templates

Following a call with @mitz-lad we agree three broad templates to build out

• landing page
• Content overview
• multiple item

As part of this we will also

• build out full place holder pattern section
• build out a more robust grid system

Bonus items

• Ability to have a template override driven from the markdown
• Content ordering step

Task to work out examples

Outcomes

Assumption is we can have data driven prototype that bridges the prototype and main site - we will able to:

• documented groups of content (i.e patterns)
• content in markdown
• macros to represent data points (i.e navigation)
• layouts and templates for each section

Who needs to know about this

@mitz-lad
@martinwake