Dynamic CMS proof
The homepage renders entirely from CMS-configured content types — zero hardcoded sections. Verified by creating a throwaway content type and watching it appear on the homepage with no code change.
0
- Proof type
- case study
- Confidence
- high
Homepage sections were hardcoded: adding a content type meant editing React components and redeploying.
Sections are built from the content-type registry at render time. A brand-new type shows up on the homepage the moment it is published — tested end-to-end with a throwaway type, then removed.
How it was measured
End-to-end test rather than a measurement: a throwaway content type was created in the admin, published, and the public homepage was reloaded without touching any code or redeploying. The type appeared as a section, then was deleted again. The "0" is a code fact — the homepage section list is built from the content-type registry at render time, so there is no hardcoded type to count.
Honest limitations
Verified once, by hand, by the person who built it. The section layouts themselves (featured cards, proof grid, timeline) are still a fixed set defined in code — it is the content types that are dynamic, not the visual templates. A new type gets a section; it does not get a bespoke design.