Reading a theme before you touch it
Why the first hour on any project belongs to the templates, not the task list.
- Start from what the template actually reads
- Change one thing at a time
- Keep the numbers next to the commit
Build guides, audit teardowns and release checklists.
Articles
50
Categories
10
Avg read
3m
This month
16
Why the first hour on any project belongs to the templates, not the task list.
Page 1 of 6
The home page after a flush is the most honest page on your site.
A dull checklist beats a brave team every single time.
Moving every escape next to its echo made the whole file easier to trust.
Custom markup for every widget, and why we stopped fighting core output.
A single slow lookup led us through a whole site's architecture.
How a class recipe list keeps templates readable and the stylesheet tiny.
Listing what runs on your site is more alarming than it should be.
The best pull request of the year removed most of a plugin.
Put the mouse away and find the bugs your users already know about.