DemandSphere moves its blog from WordPress to Jekyll, leans on AI to speed the work

Why Jekyll?

DemandSphere has completed a migration of its public blog from WordPress to the static site generator Jekyll, citing speed, easier edits and developer preference as the main drivers. Static site generators remove the database and application-server layer most CMSes rely on; content becomes markdown, layouts and frontmatter YAML. The company also pointed to a broader headless-and-markdown trend — LLMs love plain text — and the familiar security criticisms of WordPress, though reputable hosts mitigate many risks.

The migration in practice

The team migrated roughly 288 WordPress posts and a set of other pages, but they didn’t move everything. Using DemandSphere’s own GSC tools, they analyzed which pages still held search equity and which could be left behind or deleted. WordPress’ XML export provided a practical starting point; images required extra fiddling, but overall it was an export-and-import job once the content strategy was decided.

AI-assisted work

It has been reported that the migration was significantly accelerated by Claude Code, a coding agent the team used to analyze pages and automate parts of the conversion. That, the blog post claims, is what finally made the long-planned migration feasible despite a perpetually busy team and the difficulty of keeping specialist WordPress developers on the roster — a problem the author described as a “built-in brain drain.” Is this a one-off boost or a harbinger for more SSG migrations? Given current tooling and the rise of coding agents, it sure feels like the start of a trend.

In short: Jekyll won because it was familiar and fast; AI tools did the heavy lifting; and the result is a leaner, markdown-first site built for speed and agility. Not every team should rip out WordPress tomorrow, but for companies moving fast and wanting simpler edit workflows, the case is getting hard to ignore.

Sources: demandsphere.com, Hacker News