WordPress development
Fast sites your team can actually edit, and custom plugins that connect WordPress to the rest of your stack instead of fighting it.
WordPress is the right choice when people who are not developers need to change the site every week. It is the wrong choice when it is running twenty plugins that each do ten percent of what you need. A lot of my WordPress work is turning the second situation into the first.
I build themes and blocks that match your design, plugins that add exactly the feature you are missing, and the connections between WordPress and the systems where your real data lives.
What I build
- Custom themes and block patterns, so editors can build pages without breaking the layout.
- Plugins for the one feature no plugin in the directory does properly.
- REST API integrations that push leads, orders or content between WordPress and your CRM, ERP or automation layer.
- WooCommerce flows where an order triggers the right process instead of a manual export.
- Speed work: pages that load in a second instead of five.
WordPress plus automation
- A form submission fires a webhook and n8n takes it from there.
- New orders and post status changes push into the systems your team already uses.
- Content generated or enriched outside WordPress and written back through the REST API.
- Scheduled cleanups and exports that no longer depend on someone remembering.
Questions
about this
Can you work on an existing site?
Yes. I start by reading what is there. You get an honest assessment of what is worth keeping and what is costing you more than a rebuild would.
Do you use page builders like Elementor?
If your site already runs one, I work with it. For new builds I prefer native blocks: fewer moving parts, faster pages and no license that takes the layout down when it lapses.
Can WordPress talk to n8n?
Yes, and it is often the best combination. WordPress handles content and the public site, n8n handles the logic behind it. A form submission, an order or a status change fires a webhook and the workflow takes over.
Who owns the code?
You do. Everything I build is handed over in a repository with a README that explains how to run and change it.
Can you fix a hacked or broken site?
I can look at it and tell you what I find. How much is recoverable depends on what your backups still contain, so you get an assessment before you commit to anything.
Want this for your business?