Skip to main content

WordPress Development

WordPress that stays updatable

We build and maintain WordPress sites on the block editor: a theme that holds the design, plugins that hold custom behavior, and an update path that is tried on staging before it touches production.

Illustration for WordPress development services

What we build with WordPress

WordPress is PHP, a database, and a plugin ecosystem. We keep custom code in the places core updates will not erase.

  • Block themes and the Site Editor

    New sites use a block theme. Templates and template parts express the layout. theme.json carries the type, color, and spacing so editors stay inside the design instead of pasting inline styles.

    A classic PHP theme stays when the site already depends on it. We extend it with a child theme. We do not edit a parent theme that the next update will overwrite.

  • Blocks and patterns

    Repeated sections become block patterns or a small custom block. Editors insert the pattern. They do not rebuild a hero from twenty loose blocks every time.

    A custom block is registered from a plugin, with the attributes it needs and a fallback in the editor. The theme does not secretly own behavior the content depends on.

  • Plugins, including WooCommerce

    We prefer a maintained plugin when it matches the need. A custom plugin is for the behavior that should survive a theme change: a content type, an integration, a checkout rule.

    WooCommerce is in scope for catalogs, checkout, and the hooks a store actually needs. Product data and payment settings stay in WooCommerce. Presentation stays in the theme. Broader storefront engineering also sits with web development.

  • Updates, staging, and headless when it is real

    Core, theme, and plugin updates land on a staging copy first. We check the editor and the public templates, then production. A site with no staging is the first thing we add.

    Headless WordPress, with the REST API feeding a separate front end such as React, is a choice we make when the editorial team wants WordPress and the interface cannot be a theme. It is not the default.

Typical use cases

WordPress fits content sites and stores whose editors live in wp-admin and whose hosting you can update.

  • A company site on the block editor

    Pages, posts, and a small set of patterns. Marketing can publish. The theme stops them from inventing a new layout on every page, without closing the editor.

  • A catalog on WooCommerce

    Products, variations, and checkout through WooCommerce. Custom work is the piece the store needs that a setting does not cover, written as a plugin with a test on staging.

  • A site drowning in plugins

    We list what each plugin does, remove the ones that overlap, and replace a fragile combination with one custom plugin when that is smaller than the pile.

  • Editorial WordPress with a separate front end

    Authors stay in WordPress. The public site is an application that reads the REST API. We version the fields the front end depends on, so an editor change does not silently break a route.

How we work

WordPress maintenance is part of the build. A theme that cannot take an update is unfinished.

  • Separate theme, plugin, and content

    Design tokens and templates live in the theme. Behavior the content needs lives in a plugin. Posts and pages live in the database, exported when we need a copy. We do not hide PHP in a widget body.

  • Stage every update

    Staging is a copy of production with the same PHP version and the same active plugins. Updates are applied there, the editor and the public pages are checked, and only then does production change.

  • Name the load-bearing plugins

    The handover lists which plugins can be removed and which ones the theme or the content assumes. WooCommerce, a forms plugin, or an SEO plugin is called out with the version we tested.

  • Leave wp-admin usable

    Roles match the people who will log in. Patterns are available in the inserter. A custom block has a name an editor recognizes. We watch someone publish a page before we call the work done.

Tell us the theme, the plugins, and the PHP version

An existing site or a new one. We will say what belongs in a theme, what belongs in a plugin, and what should be removed.

Schedule a call

Why OLIANT

WordPress at OLIANT is a site you can update, with custom behavior in a plugin and design in the theme.

  • Updates are rehearsed

    Staging sees the core and plugin updates first. Production is the second step, not the experiment.

  • Custom code has an address

    Plugins hold behavior. Child themes or block themes hold design. Content is not the place we store PHP.

  • The editor is part of the test

    A page that looks right when we build it and breaks when an editor touches it is not finished. Publishing is part of the check.

Frequently asked questions

Questions about how we take on WordPress work.

Yes. We use a child theme and we avoid a rewrite unless the parent theme is blocking an update you need. A block theme is the recommendation for a new site, not a surprise migration in the middle of a content change.

WordPress you can update next month

Share the theme, the plugin list, and the PHP version. We will tell you what we would keep.

Illustration for the WordPress development closing invitation