Growth & Digital/Customers — scope
EDIT VIA GITHUB · /content
Section templateEditorial & standing

Customers

The proof surface — real roster, magazine treatment, outcome lines on every story.

DESIGN v1.1 LANDED AUG 31 — this scope page was written against v1; verify against the new snapshot before relying on component details.
LAYOUT MOCK — STRUCTURE ONLY
Customers layout mock
Click the mock to open the live template in the design directory (new tab).
TEMPLATE SCOPE
edit content/templates/customers.md

What this page does

Carries the social proof for every other page's claims. Magazine treatment (cover story + filterable roster) makes the real customer list browsable by industry, use case, and product — so sales can send one filtered link and any template can cross-reference a relevant story. The template renders the whole roster; adding a customer story is a content pass. Outcome lines are pending migration from the current site — that's the gating content task, flagged in the design.

Components on it

  • Cover story — the flagship customer, full bleed.
  • Sticky filter bar — industry · use case · product.
  • Story grid — the real roster (Jellyvision, Loblaw Digital, … per the design seed), one outcome line per card.
  • Outcome lines — the measurable claim per story (pending migration — flagged).
  • Story detail slots — the per-customer narrative shape the roster expands into.
  • CTA band — read more proof or Get Started.

What this page does

Carries the social proof for every other page's claims. Magazine treatment (cover story + filterable roster) makes the real customer list browsable by industry, use case, and product — so sales can send one filtered link and any template can cross-reference a relevant story. The template renders the whole roster; adding a customer story is a content pass. Outcome lines are pending migration from the current site — that's the gating content task, flagged in the design.

Components on it

  • Cover story — the flagship customer, full bleed.
  • Sticky filter bar — industry · use case · product.
  • Story grid — the real roster (Jellyvision, Loblaw Digital, … per the design seed), one outcome line per card.
  • Outcome lines — the measurable claim per story (pending migration — flagged).
  • Story detail slots — the per-customer narrative shape the roster expands into.
  • CTA band — read more proof or Get Started.
CLASS
Section template
CHAPTER
Editorial & standing
RENDERS
/customers/ + the story roster
PAGES ON THIS TEMPLATE
Customers
SPEC OWNER
Website build program