Why I build on Laravel, Craft and WordPress

Laravel

Laravel is one of the most thoughtfully-engineered PHP frameworks around. Real production stacks run on it, quietly, at scale.

It holds up under load, edge cases and real businesses. Good fit for bespoke applications, internal platforms, CRMs, workflow tools, and the kind of integration work that ties several systems together into one coherent operational flow.

Craft CMS

Craft CMS is the editorial counterpart. A flexible platform that bends to the brand instead of forcing the brand into a template. Twig templates, a clean field model, and a small surface area that keeps surprises out of production.

Reach for it when an editorial team has a strong design language and the CMS has to honour it. Hospitality sites, cultural institutions, design-led brands, the kind of work where typography and image presentation matter more than a feature list.

WordPress

WordPress is the standard CMS most agencies still run on. It carries serious editorial sites, production integrations, and Salesforce-to-WP pipes under real publishing pressure when it's used properly.

The hard parts (WP-cron pipelines, third-party API integrations, WP-CLI workflows, custom post types, the editor system, hosting moves, long-form editorial partnerships) are where the work tends to live.

And the connective tissue

Modern JavaScript, AI-pair-coding workflows, and the integration know-how that turns separate tools into a coherent operational platform. The framework is rarely the answer on its own. It's how the pieces fit together that decides whether the work lasts.