Skip to content

Tagged

Cms

3 posts on cms.

One engine, three client sites: the fork per client model

Three live sites share one CMS engine and share nothing at runtime: separate repositories, separate keys, separate databases, separate hosting accounts. The bill for that isolation arrives every time I fix something in the engine, because a fix lands in one copy and has to be carried to the rest. Here is the ritual, the path a real security fix took, and the four ways the sweep has quietly failed on me.

Two kids built games, so I gave games a content type

Lulu is 10, Otto is 11, and they are my niece and nephew. Over a handful of afternoons this summer they finished three browser games they wanted to play, and I had to decide where those games would live on my site. Three hand-written pages would have rotted by autumn, so games became a content type instead: a table, a folder scan, and a page that ends with what the game taught the kid who made it.

Real estate runs on too many dashboards

Every realtor I've worked with pays for five systems that don't talk to each other. The fix isn't another integration. It's one system that owns the whole flow, from listing to lead to closed.

← All insights