Growth & Digital/Templates
EDIT VIA GITHUB · /contentTemplates
The 16-template system and the Phase 02 experiences, each with a scope page — the mock, what the page does, and the components on it. Section templates are built once and render a whole class of pages; single pages are one-off experiences.
TEMPLATES
16
8 section templates · 8 single pages
SCOPE PAGES
24
one per template + per Phase 02 experience
EXPERIENCES
8
4 offers · 4 flows
HARDCODED HEX
0
everything binds to design-system tokens
01 · Platform
3 templates02 · Build
1 templatesTEMPLATE Build — Section template — chapter hub + 9 capability primers, one familyScope →Open template ↗
03 · Deploy
1 templatesTEMPLATE Deploy — Section template — three options (Cloud recommended), responsibility matrix, marketplace pathsScope →Open template ↗
04 · Solutions
2 templatesTEMPLATE Solutions Detail — Section template — one fixed 10-section spine × 14 sub-pages, A1–A6 proof visualsScope →Open template ↗
05 · Start
4 templates06 · Compare
2 templatesTEMPLATE Why Redis — Section template — the shape future competitor pages reuseScope →Open template ↗
Blog
1 templatesTEMPLATE Blog — One template family, three surfaces (corporate / engineering / AI) — magazine treatment, per-post sign-up CTAScope →Open template ↗
Editorial & standing pages
2 templatesTEMPLATE Customers — Section template — magazine roster, outcome line per storyScope →Open template ↗
TEMPLATE Glossary — Section template — the AEO-ready term page (Phase 03 spec)Scope →Open template ↗
Phase 02 · Offers & flows
8 experiencesScope → opens the internal scope page; Open template ↗ opens the live design. Design v1.1 landed Aug 31 — these scope pages were written against v1; verify against the new snapshot on Design and rescope where the design moved. Deliverable specs live in the website program brief; the page-by-page map is the Sitemap.