Topic
5 how-tos
Performance, deployment and operations
Find out why a page is slow
Cached or rendered, server or browser, then which part of the template: three measurements that find the cause of a slow page before anyone changes code.
Remove a query-per-row from a template loop
A lookup inside a loop runs once per row. Collect the keys first, fetch every record in one query, and read from a map inside the loop.
Cut a bundle in half with dynamic imports
Find the heavy library that most visits never use, load it only when it is needed, and measure what every page saved.
Run the go-live checklist
Launch day in the order it has to happen, with one script that checks the things people forget after the DNS switch, and the template guard that keeps staging out of search engines.
Diagnose "my change is not showing up"
The most common question on any project, answered in the order the causes usually turn out to be true, with a marker in the page that settles the first one in seconds.