Engineering
We shipped a website without a CMS. Here's why.
A small piece on the discipline of static site builds, the upload-by-FTP era, and what we keep gaining by trading some convenience for some control.
Every project we ship faces the same temptation: bolt on a CMS so the client can edit the homepage themselves. Half the time we resist it, and half the time we don’t. This post is about the half where we don’t — and why those builds tend to age better than their headless cousins.
Next entry