A case study page

The order

Every case study runs in the same sequence, and the sequence is the argument:

1. Back link, then a kicker reading “Case study”.
2. Title.
3. Deck, one or two sentences framing the problem.
4. Figure, the evidence for the claim above it.
5. Meta row: role, org, recognition. This is the MetaRow component, which CaseHero renders from its own meta prop. It is not the StatList component, which is a different thing and goes near the end.
6. Blocks: what was unclear, what was led, who was involved, what changed.
7. Artifacts, where something is still openable.
8. Pagers to the previous and next case study.

A reader who has seen one case study knows where to look in all of them. That is worth more than variety.

The figure moved once

It used to sit below the meta row at 75 percent width. It now sits between the deck and the meta row at full measure, because it is evidence for the claim in the deck and belongs beside it, not after a table of credits.

What a case study may not contain

Unverifiable numbers. Every figure on these pages traces to something checkable. A recalled statistic waits until it can be confirmed.

Proprietary material. PayPal work is shown generically. Flows are not reproduced, the plugin interface is not shown, and there are no internal names. The disclosure is a caption, not a callout.

Barred phrases. A specific list, held in the repo’s content guide, that must never appear. It exists because each entry was once wrong or unprovable.

Both places it appears

A case study is read two ways: as its own page, and injected into the dialog on the home page. The dialog fetches the real page, so there is one copy of the content. Anything added here shows in both.

Checks before you ship

1. The order above is intact.
2. Every number on the page can be traced to a source.
3. Open it from the home page deck as well as directly. Both work.
4. The page outline is one h1 followed by h2s.