Blog Websites
Why I Still Build Every Site From Scratch
People ask, reasonably, why I don't just use a template and be done with it.
Fair question. Templates are faster. Cheaper too, in the short run.
Here's the thing nobody tells you when they sell you a template: it was built for nobody in particular. It has to work for a bakery and a plumber and a photographer, all at once. That's a lot of compromise baked into one theme.
What actually goes wrong
Not the big visible stuff. The site looks fine on day one, that's the whole pitch.
It's the small stuff that piles up:
- A contact form that quietly fails on certain email providers
- Page speed that's fine until you add the fifth plugin
- A "quick edit" that turns into an afternoon because the template author renamed something in the last update
None of that shows up in a screenshot either.
The actual argument for building from scratch
It's not that hand-built is inherently better. Plenty of hand-built software is worse than a good template.
It's that when I build something myself, I know exactly why every piece is there. When something breaks, and something always eventually breaks, I'm not reverse-engineering a stranger's decisions at 11pm.
I still use libraries. I still borrow patterns that work. I'm not precious about writing everything myself for the sake of it. But the bones of the thing are mine, and that means when someone asks can we add this, I usually know the answer within the first five minutes of thinking about it, not after a day of digging through someone else's abstraction.
The honest trade-off
It costs more upfront. I won't pretend otherwise.
But I've never had to tell someone we can't do that because of how the template works. That sentence has ended more small projects than bad design ever has.
So no, I'm not switching to a template builder. Not yet, anyway.