WordPress
Sokkelund
Menus, booking and gift cards in one place
A WordPress website for the restaurant with booking, menus and gift cards gathered in one place.
Visit sokkelund.dkI have worked as a WordPress developer since version 3 and have built, repaired and taken over WordPress sites in a large share of my 400+ projects. You get custom themes without a page builder, fewer plugins and a site that is still fast in two years. And you talk directly to the person writing the code.

star reviews
Read every reviewThe choice depends on the actual problem. A plugin can suit a well-defined feature. Theme changes suit presentation and editing. An integration may need custom code when data and responsibilities cross systems. The table describes common choices rather than a rule that everything needs custom development.
| Need | Possible approach | What to assess |
|---|---|---|
| A new product-page layout | A theme template change | Editing, mobile rendering and maintenance |
| A standard feature | A well-documented plugin | Dependencies, updates and actual needs |
| Data between systems | A scoped integration | Data ownership, failures, retry and responsibility |
A purchased theme is cheap to start with and expensive to live with. You pay in speed, in code nobody can read, and in every customisation needing a child theme with thirty overrides.
I build themes from scratch with Advanced Custom Fields or blocks, depending on who is editing. The result is usually a fraction of the code and an admin interface where the fields are named something meaningful to the person using them.
WooCommerce can absolutely run a store, but it gets heavy as catalogues grow. I work on product data structure, caching strategy and the points in checkout where people typically drop off.
If you have several thousand SKUs and serious growth ahead, I will say out loud if Shopify would be a better fit. The decision is yours, but you should have the grounds for it.
A WordPress developer is a programmer who works in the code behind a WordPress site: themes in PHP, custom blocks, plugins and the database. That is different from someone assembling pages in a page builder. A page builder changes how the site looks. A developer changes how it works.
You need a WordPress developer when the built-in editor and the installed plugins no longer suffice: the theme needs adapting, the site has grown slow, two plugins fight over the same thing, or functionality has to be built that does not exist as a ready-made package.
The difference between a specialist and a generalist shows in the solutions. A generalist installs yet another plugin. A specialist knows when thirty lines of code in the theme do the same without a subscription and without extra load time. I have followed WordPress since version 3 and seen what most choices cost over a three-year horizon.
In practice I work in your existing installation, take a backup before anything else and deliver changes you can review. I build themes from scratch with ACF or blocks, and everything is documented so the next developer can take over without an onboarding call with me.
The first question with any new feature is whether a plugin exists that does it well enough. Often one does. A well-maintained plugin with many active installations, regular updates and a developer who responds to bug reports is often a better choice than something coded from scratch. There is no reason to reinvent the wheel, and a professional WordPress developer should say so out loud, even when it means fewer hours for the developer.
The problem starts when plugins become the answer to everything. Every plugin loads its own code, some of them on every single page, and every plugin is a possible way in if it is not kept up to date. If a large plugin has to be installed to solve a small task, or it needs an annual subscription for something a few lines of code can handle, I write it myself. Fewer plugins mean fewer updates to keep track of and fewer security holes.
Integrations are the other big part of WordPress development: forms that pass leads on to a CRM, sign-ups to a newsletter tool, orders from WooCommerce to an ERP or inventory system, and payment solutions in checkout. Some of them exist as ready-made plugins from the system's own vendor, and then I use those. Others need an integration through the system's API. There I write the code so errors get logged and noticed instead of disappearing without anyone seeing.
Speed is decided in the code, long before anyone installs a caching plugin. The theme should load only the scripts and CSS files the individual page actually uses, database queries should be few and targeted, and heavy lookups that rarely change can be stored temporarily so they are not recalculated on every visit. Images should use the sizes WordPress creates on upload, so a phone does not download an image meant for a large screen.
Caching is the last layer, not the first. Page caching on the server can make a slow site feel fast for visitors who are not logged in, but it hides the problem instead of solving it and helps neither in the admin nor in a WooCommerce cart. My aim is a site that passes Core Web Vitals on mobile with a good margin, even before caching is switched on. For LCP that means the largest content element on screen should appear within 2.5 seconds.
Security in the code comes down to the same few habits every time. Everything that comes in from a form or an address bar is validated, and everything shown on the page is processed so it cannot run as code. Actions in the admin are protected with security tokens (nonces) and a check of the user's permissions. Editors get the Editor role, not Administrator, and the option to edit theme and plugin files directly in the admin is switched off.
A WordPress site is not finished when it launches. The core, the theme and the plugins keep getting updates, the PHP version on the server has to keep up, and a backup is only worth something if someone has tried restoring it. Skip that for a couple of years and it is no longer one update to run but a small project where several things break at once.
Ongoing maintenance therefore consists of a few fixed tasks: updates tested on a copy before they reach the live site, a regular check that the backup can be restored, a review of plugins whose developer has stopped maintaining them, and an eye on speed so it does not slowly slip. Much of it can be handled by a technically minded employee with a good guide.
For sites I have built myself, I can handle updates, security checks and backup verification. I do not take pure maintenance contracts on sites I do not know, because maintenance requires knowing how the code fits together. In return, what needs watching goes into the documentation, so you or another developer can take over the task without guessing.
WordPress work suits remote collaboration well, and that is how I handle it for clients across Denmark. I sit in Glostrup near Copenhagen, while the sites I work on belong everywhere from Aalborg and Aarhus to Odense and southern Jutland.
Access to WordPress and hosting is all it takes to get started. From there the dialogue runs on email and video, and you can follow the changes continuously instead of waiting for a monthly status.
Many of my clients come from an agency setup where every small fix had to pass through a project manager and be priced as a task. With a freelancer you write directly to the developer, get a fast answer and do not pay for a layer of coordination on top of the actual work.
I do not start new projects in Elementor, Divi or WPBakery. They are the single factor that most often ruins performance on Danish WordPress sites, and they make content hard to move later.
It is worth knowing what you are committing to. Content built in Elementor sits as Elementor's own data structure in the database. Switch the plugin off and you are left with a page full of shortcodes. That is a real cost of switching, and it rarely comes up when the theme is sold.
I can happily maintain a site already running on a page builder, and I do not propose a rebuild just because I would have done it differently. But when we talk about something new, I build it without one.
Concrete deliverables, not a report of recommendations someone else has to find time for.
Built with ACF or blocks depending on who edits, without the layers a purchased theme drags along.
A map of what is actually used and what each plugin costs in load time. The rest gets solved in the theme.
Including fixes for the code that snaps under new PHP versions, before it becomes urgent.
Stale transients, revisions and leftover tables from plugins deleted long ago.
WordPress
Menus, booking and gift cards in one place
A WordPress website for the restaurant with booking, menus and gift cards gathered in one place.
Visit sokkelund.dkWordPress
Design focused on conversion
A new WordPress website for private and business customers with design, tracking and a simpler booking flow.
Visit 3x34.dkWordPress
WordPress built to keep up
A custom theme with flexible templates for Dinero's product pages, pricing and guides.
Read about my work for DineroVisit dinero.dkWordPress
From class schedule to booking
A WordPress website for the studios with class schedules, pricing and a clear route to booking.
Visit energii.dkWordPress
10 museums gathered in one website
A WordPress website bringing together museums, experiences and visitor information from across Ringkøbing Fjord.
Visit ringkobingfjordmuseer.dkFour steps. You know what happens when, and you can stop after any of them.
A 20-30 minute call where you describe what needs to be built or repaired. I ask about platform, access and deadline, and tell you honestly if the job sits outside what I am good at.
Small jobs get a price after a short clarification. If a larger existing project needs a technical review first, we agree the price and scope of that review before I open the code.
You get a firm agreement on what is included, what is not, and when it will be ready. If the scope changes along the way, we deal with it openly instead of letting it drift.
I work in your own repository and your own hosting and deliver in pieces you can see and approve. When we are done, you have the code, the access and documentation that makes you independent of me.
It depends on the job: a new theme costs more than a bug fix, and the price is driven by design complexity, the number of integrations and the state of the existing code. Write what you are facing, I will ask the necessary questions and give a concrete quote, with a same-day reply.
WordPress itself is free. What costs money each month is hosting and the domain, plus licences for any paid plugins or a theme. On top of that comes maintenance: updates to core and plugins, backups and monitoring, handled either by you or by a developer. Hosting is the line not worth saving on, because cheap shared hosting is one of the most common reasons a WordPress site is slow.
Builds and maintains the code behind WordPress sites: themes, blocks, plugins, integrations and the database. Everything beyond what the built-in editor can handle.
Yes. When a feature does not exist as a ready-made plugin, or the ready-made one is too heavy or needs a subscription for something simple, I build it as a small plugin for your site. Functionality that has to survive a theme change goes in a plugin rather than in the theme, so it does not disappear the day the theme is replaced. The code is documented, and it is yours.
Everything can happen online, and it does for most of my clients in Aarhus, Odense, Aalborg and the rest of the country. If you are in the Copenhagen area, I am also happy to meet in person for a kickoff.
Yes, it is a large part of my work. I read through the code first and tell you honestly whether building on it or starting over makes more sense. Sometimes the answer is to build on it even though the code is ugly.
Not for new projects. I happily maintain sites already running on them, but new work I build with custom blocks or ACF, because it gives a faster site and content that can move.
To a limited extent and only for clients I have built for: updates, security checks and backup verification. I do not take pure maintenance contracts off the street.
It depends on the type. A bug fix or a smaller change is typically a job of hours or a few days. A new WordPress site with ten to fifteen pages usually takes four to eight weeks from approved design. Integrations and custom plugins I estimate once I have seen the systems they need to talk to, and the timeline goes in the written quote.
I have worked with both many times. Multiple languages is rarely technically hard, but it doubles the amount of content someone has to keep current, and that cost belongs in the decision.
Write a few lines about what needs doing and send the site's address if it already exists. Then we have a short call about the job, access and deadline. For larger existing projects I read through the code before you get a written quote with a clear scope. When the work begins, I take a backup before touching anything.
Send your website URL, what you need solved and your desired deadline. I will assess the next step and describe what the quote includes. Larger investigations are agreed separately before work begins.
Describe your taskYour next step
Tell me about your project. I’ll get back to you with questions, options and a concrete next step.