Work
Work I wrote, edited or collaborated on for somebody else’s site, plus the research and essays here that belong with it.
275 pieces / 6 publications
The shortlist
If you only have time for 6 of my pieces, I’d start with these. Each one shows me doing something different, whether that’s breaking a store on purpose or making the case for WordPress to CTOs.
A WooCommerce store whose checkout, admin, and product pages I slowed down on purpose. Then I used Kinsta APM to trace each fault to the plugin behind it.
As I published it
Which PHP version runs WordPress, Drupal, Laravel, and 11 more fastest, with every score published. I set up all 14 platforms and benchmarked them across 5 PHP versions.
A step-by-step guide to PostgreSQL replication on Ubuntu, failover included. Highgo, a PostgreSQL company, later used it as a source for their own tutorial.
As I published it
Setup steps for each cache, then stress tests against a baseline with no caching at all. Both ran on the same $10 DigitalOcean server, and I picked a winner.
Actions and filters, taught through worked examples, then custom hooks of your own. It starts with how they work and ends with a plugin other developers can extend.
As I published it The code, on GitHub
The case for WordPress, made to CTOs and CMOs. rtCamp’s writing briefs ask applicants for an article with this piece’s exact title. I wrote the one they published.
As I published itI build the kind of thing I write about. It makes the writing faster and the technical reviews shorter.
Naming, identity, and voice. Same job as writing, different medium.
Launches, positioning, and the calendar that holds it together.
Compares 6 Kentico alternatives, among them WordPress, Sitecore, Contentful, and Drupal, on ownership, editorial speed, and 5-year cost.
Compares 6 Kentico alternatives, among them WordPress, Sitecore, Contentful, and Drupal, on ownership, editorial speed, and 5-year cost. Written for teams facing Xperience 13’s end of life on December 31, 2026.
For sites moving off Craft CMS, it lays out how the content, structure, and integrations come over to WordPress with no data loss or downtime.
Pitches one governed WordPress Multisite, built on OnePress, to companies running each brand’s site on a separate CMS, with one codebase and one dashboard for every brand.
Covers how the move from Optimizely to WordPress carries over content, integrations, and SEO, through go-live, without losing data.
Covers the eleven strongest Contentful competitors in 2026, split across headless CMS replacements and enterprise DXP upgrades, each matched to the specific constraint it resolves.
Argues that a website should be treated like a product with a roadmap instead of a project you rebuild every three years. It makes the money…
Argues that a website should be treated like a product with a roadmap instead of a project you rebuild every three years. It makes the money case to the executives who approve the budget.
A decision-framework guide for enterprise teams leaving Contentful, covering architecture, Rich Text transformation, SEO preservation, and the…
A decision-framework guide for enterprise teams leaving Contentful, covering architecture, Rich Text transformation, SEO preservation, and the real cost of ownership. Weighs traditional against headless WordPress instead of assuming one.
Written for teams leaving Contentful, with rtCamp’s promise of a clean data transfer and SEO continuity, and the numbers from its past work.
Weighs custom WordPress development against commercial themes for enterprise sites on performance, security, integrations, and total cost, and…
Weighs custom WordPress development against commercial themes for enterprise sites on performance, security, integrations, and total cost, and names the uses where an off-the-shelf theme still works.
The questions a company should ask before hiring a WordPress partner, and what the answers tell you about whether that partner can deliver.
Lists the business and technical signs that an in-house WordPress team has hit its limit, what waiting costs, and how staff augmentation adds…
Lists the business and technical signs that an in-house WordPress team has hit its limit, what waiting costs, and how staff augmentation adds expert developers without a long hiring cycle.
Breaks down what offshore WordPress development actually costs versus onshore rates, using industry-wide figures, so enterprise buyers can judge the trade-off for themselves.
Compares Arc XP and WordPress for publishers on cost, vendor stability, architecture, editorial workflow, AI readiness, and compliance, and says when Arc XP is the right call.
A complete guide for publishers leaving Arc XP, The Washington Post’s publishing platform. It covers moving your content out safely and keeping…
A complete guide for publishers leaving Arc XP, The Washington Post’s publishing platform. It covers moving your content out safely and keeping your Google rankings through the switch.
Makes the case to publishers on Arc XP that WordPress is the way out, and walks through a migration that keeps every URL, subscriber, and pageview.
An enterprise evaluation of the strongest Drupal alternatives in 2026, weighing each platform on developer availability, long-term cost, and the effort to migrate.
Defines enterprise WordPress as true enterprise software: auto-scaling infrastructure, accountable publishing workflows, compliance, and multi-brand orchestration.
Makes the case for WordPress to enterprises facing rising SaaS bills, covering who runs on it, open-source ownership, the talent pool…
Makes the case for WordPress to enterprises facing rising SaaS bills, covering who runs on it, open-source ownership, the talent pool, multibrand governance, and what the Abilities API adds next.
No matches. Loosen a filter, or take my word for it.