Expertise

Freelance WordPress developer

Freelance WordPress developer for brochure and editorial sites

Want an editorial site you update yourself, without depending on a developer for every last comma? WordPress does that very well — as long as it's built cleanly.

Kylian Bellegarde, freelance WordPress developer in Martinique, at work integrating a custom theme.
Custom themes or advanced customisation of premium themes.
ACF and Gutenberg to give editors real autonomy.
Optimised performance, Core Web Vitals and technical SEO.

WordPress remains unbeatable for brochure sites, blogs and editorial sites that need to stay self-sufficient on the content side. I build WordPress without shortcuts: custom themes, ACF, Gutenberg, clean technical SEO and security taken seriously.

WordPress powers a huge share of the web, and that's no accident. For a showcase site, an institutional site or an editorial blog, it's the most pragmatic tool out there: you write your pages and posts in an interface everyone already knows, you publish on your own, and you don't need to call me to change an opening time or add a piece of news. That autonomy is the real value of WordPress, and it's exactly what most of the organisations who reach out to me are looking for.

Where I make the difference is in how it's built. A WordPress site stacked with random plugins, on a downloaded and tinkered-with theme, ends up slow, fragile and impossible to maintain. I work the other way around: a clean foundation, the fewest plugins possible, code I understand and that whoever comes after me can pick up. I structure content with ACF (Advanced Custom Fields) so your pages have clear fields rather than one big catch-all block of text, and I build custom Gutenberg blocks when the editor needs to lay things out without breaking anything.

In concrete terms, that means you get a back office that looks like your site, not like a puzzle. A "team member" entry has a name field, a photo field, a role field. A "service" page comes with its sections already framed. You fill it in, you publish, and the result stays consistent. It's that editorial discipline that separates a WordPress site that ages well from one you'll have to rebuild in two years.

The kind of projects where WordPress is unbeatable is anything built around content: a company site with service pages, an association or local authority that publishes regularly, an independent professional, a restaurant, a tourist accommodation, a blog that supports your SEO strategy. If you need several languages, the ecosystem handles it cleanly (Polylang, WPML). The right instinct is to start from the content you'll actually manage and derive the structure from it — not the other way around. It's that upfront scoping that keeps you from working around your own site to publish a page six months later.

You often hear that WordPress is slow or insecure. That's false when it's done well, and true when it's neglected — so everything comes down to execution. On speed, I start from a lightweight theme, set up serious caching (most often WP Rocket), compress and serve images in the right format, and load only what's strictly necessary. The goal is simple and measurable: Core Web Vitals in the green, verified in the browser and not just on some forgiving testing tool.

Performance also depends on where the site is hosted, and that's a point too often overlooked. Cheap shared hosting drags down even the best settings; conversely, decent hosting (a dedicated WordPress plan, or a properly configured and secured VPS) changes everything in how the site feels. I advise you based on your real traffic and your budget, without selling you an oversized infrastructure you don't need. The idea is for the machine to match the site, no more and no less.

Technical SEO is part of the work, not an option billed separately. Clean heading structure, readable URLs, structured data (schema.org), Open Graph tags, a sitemap, careful redirect management when taking over an existing site. WordPress remains one of the best foundations for editorial SEO: it's designed for content, and content is what gets you ranked. I use Yoast or Rank Math to give writers clear guidance, without turning every article into a chase for green dots.

If you're targeting a local audience in Martinique or the Caribbean, local SEO is something you work on concretely: well-targeted pages covering your areas and your services, a business listing connected to the site, local business structured data, consistent contact information. WordPress lends itself perfectly to this kind of groundwork, because it lets you create and maintain as many useful pages as your business calls for, without depending on me for every addition.

Security, finally, is mostly a matter of rigour. I harden the admin area, disable what serves no purpose (XML-RPC in particular), keep PHP and the plugins up to date, and add a layer such as Wordfence or an application firewall depending on the context. The field truth is that almost every hacked WordPress site is hacked because of an abandoned plugin or a weak password — not the WordPress core itself. Regular maintenance costs far less than an emergency restore.

A large part of my WordPress work isn't building from scratch: it's rescue work. A site that drags, plugins stepping on each other, an outdated PHP version, security alerts, or simply a theme that's become impossible to evolve. Before touching anything, I start with an audit — performance, security, code cleanliness, plugin status, SEO health — then I give you a prioritised action plan. You know what's serious, what can wait, and what it costs, before I change a single line.

I work with backups and a staging environment, so I never experiment directly on the live site. Depending on the assessment, we clean up the unnecessary plugins, bring PHP up to date, fix the performance bottlenecks, recover lost SEO positions, and sometimes rebuild the theme cleanly while keeping the content. The point isn't to tear everything down for the pleasure of starting over: it's to stabilise what can be stabilised and only rebuild what truly deserves it.

Upgrading the PHP version is the most common case, and also the most sensitive: a site left on an obsolete version becomes slow, vulnerable, and eventually breaks when the host drops support. I test the upgrade in staging, spot the plugins or theme snippets that aren't compatible, fix or replace whatever gets in the way, and only go live once everything works. You don't wake up one morning to a broken site because an update was forced through.

On the choice of theme, I adapt to your budget rather than to a dogma: a fully custom theme when the design demands it, heavy customisation of a solid premium theme (GeneratePress, Kadence) for good value for money, or a clean page builder (Bricks) when layout autonomy comes first. In every case, I explain the trade-off. And being based in Martinique, I'm in your time zone: no twelve-hour gap to recover a site stuck on a Monday morning, and a single point of contact who replies in French.

I always deliver with a handover: a short video showing you how to publish and edit your content, a written guide, and 30 days of support included after launch for adjustments and questions. My goal is for you to be self-sufficient day to day — not for you to stay tied hand and foot to your provider. If you want to manage your site on your own afterwards, perfect. If you'd rather hand the maintenance to me, we set up light ongoing support (updates, backups, monitoring).

That maintenance is the cheapest insurance you can take out on a WordPress site. In practice: I keep the core, the theme and the plugins up to date, I check that backups are running and can actually be restored, and I keep an eye on security and speed. Ninety percent of the compromised sites I recover got that way for lack of this kind of follow-up. A few minutes of regular checks are far better than a day of emergency repairs with the site offline the whole time.

I'm honest about the tool's limits, because choosing the right foundation from the start saves months of frustration. If your project is really a business application with strong logic — a complex client area, automations, calculations, fine-grained access rights — WordPress isn't the best choice and I'll tell you so: we'll go with Laravel instead. For an online shop, WooCommerce extends WordPress very well up to a certain volume. The right tool depends on your real need, not on what I'd rather sell.

For e-commerce, the line is fairly easy to draw. As long as you're selling anywhere from a few products to several hundred, with a standard checkout flow, WooCommerce is an excellent choice: you keep WordPress's autonomy, with no commission on your sales. Beyond that, with very large catalogues or genuinely unusual e-commerce rules, we look together at whether a custom stack or another platform would be a better fit. Either way, we talk it through frankly before you commit, so we don't build on a foundation that will hold you back a year from now.

The advantages

  • Real editorial autonomy: you publish and edit your content on your own, in a familiar interface, without depending on me for every detail.
  • A clean foundation and a minimum of plugins, with readable code any developer can pick up after me.
  • Content structured with ACF and custom Gutenberg blocks: clear fields rather than one big text block that's impossible to keep up over time.
  • Careful performance: a lightweight theme, caching, optimised images and Core Web Vitals verified in the green in the browser.
  • Technical SEO included from the start: clean structure, structured data, and controlled redirects when taking over a site.
  • A single point of contact based in Martinique, in your time zone, who replies in French and without jargon.

Limitations to be aware of

  • WordPress quickly shows its limits on applications with heavy business logic (calculations, fine-grained rights, automations): there, a framework like Laravel is a better fit.
  • Its security depends on maintenance discipline: an abandoned or un-updated plugin remains the leading cause of a compromised site.
  • The richness of the plugin ecosystem is both a strength and a trap — piling on too many weighs the site down and creates conflicts; I prefer to install as few as possible.
  • For very large shops or e-commerce needs that go beyond the ordinary, WooCommerce or a custom stack may be more appropriate — we talk it through frankly before getting started.

WordPress isn't the answer to everything. The right criterion isn't the trend of the moment, it's the nature of your project: content to publish, or genuine application logic to run. Here's how I decide with my clients.

Choose WordPress if…

  • Your site is above all editorial: showcase, institutional, blog, news, presentation pages.
  • You want to manage and publish your content with full autonomy, without calling on a developer for every change.
  • You're after a controlled, predictable budget, with affordable hosting and light maintenance.
  • Ranking your content is a priority and you want a solid SEO base from day one.
  • You need to move fast on standard features (forms, newsletter, multilingual) thanks to proven plugins.

Prefer something else if…

  • Your project is a genuine business application: a rich client area, automations, calculations, complex access rights (look to Laravel or Symfony instead).
  • You have heavy, specific functional logic that plugins will never cover cleanly.
  • You're planning a shop with a very large catalogue or e-commerce with unusual rules (let's look at WooCommerce or a custom build).
  • Your interface calls for advanced interactivity, real time, or a true app-like feel (React comes into play).
  • You want full control over the architecture and every behaviour of the system, without depending on third-party updates.

  • Brochure and institutional sites
  • Editorial blogs with advanced SEO
  • Taking over and modernising existing WordPress sites
  • Maintenance, security and ongoing support

Editorial autonomy

Your teams publish on their own: articles, pages, images. You no longer have to come to me for every change.

Rich ecosystem

ACF, Yoast, WooCommerce, WP Rocket: thousands of proven plugins to move fast on the standard features.

Controlled cost

Fewer hours of pure development than fully custom work, a predictable budget, low-cost hosting, light ongoing maintenance.

01

Technical choice

A custom theme or a customised premium theme, depending on budget and specifics.

02

ACF + Gutenberg structure

Content modelling with ACF, custom Gutenberg blocks for editorial autonomy.

03

Optimisation

Performance (cache, images, lazyload), SEO (Yoast + structured data), security (Wordfence or iThemes).

04

Training and delivery

A walkthrough video, a written guide, and 30 days of post-delivery support included.

FAQ

Depending on the budget: a 100% custom theme (Bedrock + Sage), customisation of a premium theme (GeneratePress, Kadence), or a lightweight page builder (Bricks, Oxygen).

A WordPress project? Let’s talk.

I scope out your needs and tell you honestly whether WordPress is the right choice for your project.