Opens in a new tab
Technologies & Tools

The technologies behind our WordPress development.

We work across WordPress, WooCommerce, front-end and back-end development, integrations and hosting infrastructure. We choose tools to suit each project, and we are clear about which ones we build with every day and which we support when a project needs them.

How to read this page
Core toolsWhat we build with every day.
Used on projectsHands-on whenever a project calls for them.
Supported when scopedWe integrate with or work alongside these, agreed per project.
WordPress builders

Builders, and how we choose between them.

Each builder suits a different workflow. We work in several, so the choice follows the project and the people who will maintain it, not our habits.

Breakdance

Core tool

Our primary builder. We use it for design-led, component-based builds, with custom code where a layout or behavior needs it.

Often chosen for: A new build, or a site your team will keep editing visually.

Elementor

Used on projects

Familiar territory on existing sites: customizing, extending and carefully changing builds that are already in production.

Often chosen for: Sites already on Elementor, or agencies standardized on it.

Bricks

Used on projects

Part of our workflow, and the builder behind this website. Suited to structured, class-based builds with lean output.

Often chosen for: Projects that favor a developer-friendly structure.

Gutenberg

Used on projects

Native block editor workflows for projects that call for a lighter, more standard editing experience.

Often chosen for: Content-led sites with simple editing needs.

How we choose

Four questions shape the recommendation, and we settle them in scoping.

  1. What does your agency already use?

    Continuity matters. Where it makes sense, we work inside your existing builder.

  2. Who edits the site later?

    The editing experience should suit the people who maintain the site.

  3. How custom are the layouts and data?

    More bespoke designs and content models point towards different tools.

  4. What does upkeep look like?

    Performance and long-term maintenance weigh into the decision.

Frameworks and plugins

Structure that stays easy to edit.

A good WordPress build starts with a clean content model. We pair custom post types, taxonomies and fields with a small set of dependable plugins, so your team edits content, not code.

Content structure

Advanced Custom Fields (Core tool)
Custom field groups and flexible layouts, with templates that read from them.
Custom post types and taxonomies (Core tool)
Content models built around how your content is actually organized.

Content operations

WP All Import (Used on projects)
Structured imports of posts, products and custom data, with mappings checked before anything goes live.
WPCode (Core tool)
Managed code snippets deployed safely, instead of edits in theme files.

Forms

Gravity Forms (Core tool)
Multi-step forms, conditional logic and notifications, connected to the services behind them.
Fluent Forms (Supported when scoped)
Where a project or agency already uses it, we work with it.

Technical SEO setup

Rank Math (Used on projects)
Meta, sitemaps, redirects and schema, set up cleanly at build time.
Yoast SEO (Used on projects)
The same technical setup, where it is already part of your stack.

SEO plugins are configured as part of a build, so the site is technically sound for whoever manages search strategy. We do not offer SEO as a standalone service.

WooCommerce development

Stores built around how you sell.

WooCommerce is more than a plugin install. We follow an order from the product catalog to the carrier, and build or connect each part so it fits your business.

  1. Product data

    Attributes, variations, imports and inventory rules kept consistent.

    products
  2. Pricing and access

    Wholesale roles, customer-specific pricing and ordering rules, as scoped.

    b2b
  3. Checkout

    Fields, validation and flow tailored to how you sell.

    checkout
  4. Payment

    Gateways connected and tested across the paths customers actually take.

    gateway
  5. Shipping

    Carrier APIs for rates, labels and tracking, where the carrier supports them.

    carrier api
  6. Extensions

    Custom WooCommerce extensions when off-the-shelf plugins do not fit.

    plugin

Built to be maintained. Where a requirement does not fit an existing plugin, we build a focused extension rather than stacking workarounds.

WooCommerce Development →
Development technologies

The code underneath the builders.

Builders only go so far. When a project needs custom behavior, an integration or a separate front end, we write the code, on a classic WordPress stack or a headless one.

HTML and CSS (Core tool)
Semantic, accessible markup and responsive styling. The foundation of every build.
PHP (Core tool)
Themes, plugins and hooks: custom functionality that belongs inside WordPress.
JavaScript (Core tool)
Interactive behavior, from small enhancements to application logic.
MySQL (Used on projects)
Understanding the WordPress database: queries, data structure and migrations.
REST APIs (Used on projects)
Consuming and exposing endpoints for integrations and separate front ends.
React and Next.js (Used on projects)
Modern front ends for headless projects.
WPGraphQL (Supported when scoped)
A GraphQL layer over WordPress content, when a headless project calls for it.
Headless WordPress architecture (Used on projects)
WordPress as the content system behind a separate front end.
Automation and integrations

Connecting WordPress to the rest of your stack.

Most websites sit among other systems. We connect them so information moves without manual re-entry, and we keep each connection simple enough to maintain.

  1. event

    Something happens

    A form is submitted, an order is placed, a record changes.

  2. webhook

    A webhook fires

    WordPress sends or receives the event as it happens.

  3. api

    An API call connects

    Data moves between WordPress and another system.

  4. workflow

    The workflow runs

    The record is routed, updated or passed to the next tool.

  5. confirm

    The result is checked

    Failures are caught and handled, not discovered later.

Webhooks

Event-driven connections that send or receive data between WordPress and other services.

API integrations

Connections to payment, shipping, CRM and other third-party services through their APIs.

Workflow automation

Routing form entries, orders and records to where they need to go, with confirmations.

Integration platforms

We work with the platform your team already uses, and recommend a simpler path where one exists.

Performance, security and infrastructure

Fast, protected and safe to change.

Where a site is hosted and how changes reach it matter as much as the code. Here is what we work hands-on with, and what we support alongside your own setup.

What a visitor passes through

  1. CloudflareDNS, CDN and SSL at the edge
  2. WP EngineManaged hosting and server-side caching
  3. WordPressApplication caching and optimized delivery

How a change reaches the live site

  1. GitVersion control for code changes
  2. Staging environmentReview and test away from production
  3. ProductionRelease, then verify key workflows

Hands-on experience

Tools and practices we use directly on projects.

  • WP Engine
  • Cloudflare
  • Caching
  • SSL setup
  • Git
  • Staging environments
  • WordPress migrations
  • Performance optimization

Supported alongside

We work within these rather than replace them. The details are agreed per project.

  • Hosting platforms your agency already uses
  • CDNs and edge services outside our core setup
  • Server administration handled by your host or team
  • Monitoring and scanning tools already in place
Start a conversation

Have a technical requirement to talk through?

Tell us about the stack you are working with and what the project needs. We will tell you plainly where we are hands-on, where we would support, and how we would approach it.