Growth & Digital/Compare — scope
EDIT VIA GITHUB · /content
Single page06 · Compare

Compare

Chapter 06 anchor — the criteria-led comparison for shoppers, off the top nav by design, paired with paid search.

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
Compare layout mock
Click the mock to open the live template in the design directory (new tab).
TEMPLATE SCOPE
edit content/templates/compare.md

What this page does

Converts comparison shoppers — the highest-intent segment paid search can buy. It maps workloads to the right Redis fit, makes the "beyond caching" argument (cache and database collapse into one system on hot paths), and compares on criteria a buyer can verify: tail latency, Active-Active geo-distribution, workload coverage. Off the top nav by locked decision — reached from the footer, the chapter spine, and competitor-term campaigns, so its message match with paid ads is part of the spec.

Components on it

  • Compare hero — direct, criteria-led framing; no vendor-page hedging.
  • Comparison table — criteria rows × options, verifiable claims only.
  • Workload mapping — which workloads Redis wins and why, in the buyer's terms.
  • "Beyond caching" narrative — the platform argument against single-purpose alternatives.
  • Proof band — benchmarks (tail latency, Active-Active) + customer evidence.
  • CTA band — Get Started; message-matched with the paid competitor campaigns.

What this page does

Converts comparison shoppers — the highest-intent segment paid search can buy. It maps workloads to the right Redis fit, makes the "beyond caching" argument (cache and database collapse into one system on hot paths), and compares on criteria a buyer can verify: tail latency, Active-Active geo-distribution, workload coverage. Off the top nav by locked decision — reached from the footer, the chapter spine, and competitor-term campaigns, so its message match with paid ads is part of the spec.

Components on it

  • Compare hero — direct, criteria-led framing; no vendor-page hedging.
  • Comparison table — criteria rows × options, verifiable claims only.
  • Workload mapping — which workloads Redis wins and why, in the buyer's terms.
  • "Beyond caching" narrative — the platform argument against single-purpose alternatives.
  • Proof band — benchmarks (tail latency, Active-Active) + customer evidence.
  • CTA band — Get Started; message-matched with the paid competitor campaigns.
CLASS
Single page
CHAPTER
06 · Compare
RENDERS
1 page — /compare/
PAGES ON THIS TEMPLATE
Compare
SPEC OWNER
Website build program