Fixes · Diagnostics
Diagnostics for Strapi builds that aren't behaving.
Most Strapi problems aren't Strapi problems. They're implementation choices that were reasonable at ten content types and stop being reasonable at four hundred: a population strategy nobody revisited, a content model designed by backend engineers, a query that got slower every month until someone noticed.
These pages are what I check, in what order, when something's wrong. Each one takes a single symptom, works through the likely causes from most to least common, and tells you how to confirm which one you've got before you change anything.
01
Performance
Where nearly every 'Strapi is slow' ticket ends up.
02
Content architecture
Decisions made at ten content types that stop working at four hundred.
03
Before you launch
The fortnight before go-live, in the order failures actually happen.
These are living pages, reviewed and updated rather than dated and abandoned. If something here is wrong or out of date for your version, tell me.
S/01
Performance & Architecture Rescue
Need this diagnosed on your own project rather than in the abstract? That's S/01 — Performance & Architecture Rescue.