WordPress developer · Based in Denmark
Custom WordPress.
No builders.
I’m Aris. I take your design and build it into WordPress from scratch: a custom theme on WordPress’s own block editor, with no Elementor, no Divi and nothing you’re stuck with later. Then I keep it running.
No page builder. No forty plugins. No “it’s probably fine.”
Your site should be fast, survive a WordPress update on its own, and make sense to the next developer who opens it. Ideally without them swearing at you.
From Figma to a site your team actually uses
I’ve spent over 20 years building WordPress sites that other people have to live with after I hand them over. That one constraint shapes everything I do.
Most of my projects start with a design file. I build it as a custom theme, block by block, so what you approved in Figma is what goes live. There’s no bought template underneath to fight with.
Your editors get blocks made for your content. They can add a page, a case or a news story without calling me, and without breaking the layout.
If you have content on an old site, I move it over. On my last large build the client barely had to copy and paste a thing.
When the site has to talk to another system, like a member portal, a CRM or an ERP, I write the integration myself. Custom API endpoints, built for that system.
Fixed price, fixed scope. You get the number before I start.
How I got here
Different clients.
Same standard.
Recent work
- National member organisation: custom theme from Figma, API endpoints to an external member portal, full content migration
- Executive search firm: custom theme from Figma, cases, team profiles and job listings
A union and a recruitment firm want very different things from a website. One needed its site wired into a member portal, with advice, events and a magazine on top. The other needed to look sharp in front of executives and keep its job listings current.
Both started as a Figma file. Both got a theme written for them, and an editor their own people can use. I wrote the code myself, start to finish.
I take a handful of projects at a time. That’s how many I can do properly while still picking up the phone for the ones I finished last year.
What I actually do
One person, from the Figma file to the server. These are the jobs I get hired for.
Most of my work
Custom WordPress themes
You bring the design. I build it as a block theme from scratch, with blocks shaped around your content, so your team can run the site day to day without breaking the layout.
Integrations & custom blocks
Member portals, CRMs, ERPs, booking flows. When your site has to talk to another system, I write the API endpoints for it.
WooCommerce
Shops with a checkout that just works, and product data that stays tidy as the catalogue grows.
Speed & server
If it’s slow, I find out why: caching, queries, images, hosting. Installing another plugin and hoping isn’t on the list.
Migrations
Off Elementor, off Divi, off a bad host. URLs kept, redirects mapped, content moved for you.
Launch day is day one.
A WordPress site needs looking after. With an SLA, that’s my job.
I keep WordPress, plugins and theme up to date, take backups, watch the site and step in when something breaks. You get support when you need a hand, and a fixed response time you can count on.
It doesn’t matter who built your site. If it runs WordPress, I can take it on. Running a shop? There’s a WooCommerce add-on.
Every site is different, so we set the SLA up to fit yours.
Three things I won’t budge on.
01
No page builders
WordPress’s own editor does the job. A builder is lock-in, and you pay for it the day you want to leave. Everyone wants to leave eventually.
02
Fixed price, fixed scope
If the scope changes, we agree on it before I do the work. No creeping hours, no awkward invoice in month three.
03
You own everything
Code, hosting, domain and every account, in your name from day one. If you’d rather work with someone else next year, nothing is holding you here.