Content engineering / WordPress
Custom WordPress development.
Built around your content.
Themes, plugins, WooCommerce stores and headless WordPress back ends for founders, marketing teams and product leads. Start with what your editors publish and the workflows your customers use, then agree the architecture and handover.
Discuss WordPress requirements โContents ยท WordPress
One content model. Clear places for code.
A custom WordPress build starts from your content: custom post types for the things you publish, such as case studies, locations, courses or products; structured field groups so editors fill in fields rather than styling text by hand; and blocks designed for your layouts. Functionality belongs in a plugin and presentation belongs in the theme. WordPress itself recommends registering custom post types in plugins so the content remains portable when the theme changes.
The proposed scope can include a custom theme, custom plugins, a selected set of maintained third-party plugins and a staging environment where your team reviews changes before launch. A marketing site, a WooCommerce store and a separate app are different deliverables. Identify which ones the project actually needs rather than treating a catalogue product as a WordPress build.
- Corporate, membership and course content: model the records, permissions and editorial workflow.
- WooCommerce: specify catalogue, cart, checkout, orders and operational integrations.
- Headless content: agree the API, preview and publishing experience as well as the front end.
- Delivery: define staging, release approval, backups, documentation and receiving-team access.
Branding, source and support are contract subjects.
White-label branding, confidentiality, IP assignment and post-launch support need written terms for the actual engagement. Identify the custom theme, plugins, repositories and documentation to be handed over. Separate custom work from WordPress, third-party packages, premium plugins, licensed media and hosted services. A source-code handover does not erase those licence terms.
Agree the bug boundary, maintenance responsibilities, support period if any, escalation route and change-request process. Record confidentiality, response expectations and custom/third-party rights in the engagement terms.
WordPress, Drupal or a custom application?
The platform choice affects who edits the site, where data and permissions live, how it is hosted and what future changes need. Use the same content examples and operating requirements to compare alternatives. Do not decide from a theme count, plugin count or blanket fastest-platform claim.
- Editorial workflow: which staff can draft, review, translate, schedule and publish each content type?
- Content relationships: which records reference one another, and how are they queried and exposed?
- Application logic: what is ordinary publishing, and what requires per-user state, real-time updates, complex transactions or calculations?
- Extensions: which maintained modules or plugins meet the requirement, and what needs custom code?
- SEO controls: titles, descriptions, canonical URLs, structured data, redirects and sitemap ownership must work in the actual chosen front end.
- Operation: compare hosting, premium licences, patching, monitoring and the receiving team's ability to maintain the result.
Evaluate WordPress when publishing and structured content are central. Evaluate Drupal against the specific editorial and relationship needs rather than assuming every institution needs it. Evaluate a Laravel, Node.js or other custom application when the product requirements call for that architecture. A headless approach is another trade-off, not a shortcut that removes operational work.
Seven questions before a custom WordPress build.
What does a custom WordPress build give you that a theme does not?
A marketplace theme can be a useful starting point, but its design and feature choices may not match your content. A custom build can define your own content types, field groups, templates and blocks. Keep the content model in a plugin rather than relying on a theme to register it, and make the editor experience part of acceptance.
For each content type, record fields, required values, relationships, authoring permissions, revisions, archive pages and URL structure. For each page layout, decide which parts an editor can change and which are protected. Evaluate ACF, native block attributes or another field approach against the model and its licence, rather than making one extension mandatory for every project.
When is WordPress the right choice, and when is it not?
Marketing sites, blogs, documentation, memberships, course sites and stores all have different requirements. WordPress can be evaluated where content creation and publishing matter, with plugins considered for forms, SEO, translation, payments or learning. Check the actual extension, data flow and editor workflow before treating a plugin category as a completed feature.
If the product is mainly per-user dashboards, real-time data, complex permissions or heavy calculations, compare a custom application or a hybrid architecture. Do not force every workflow into posts and metadata without examining the data model. Equally, do not claim that an application requirement automatically rules WordPress out: document the limits and the components that would carry the custom work.
How does WooCommerce plugin development work?
A WooCommerce extension should use its supported hooks and APIs rather than editing core files that updates replace. Scope pricing and discount rules, shipping by weight or zone, subscriptions, business catalogues, product importers and ERP, CRM or warehouse sync as separate workflows. Each extension needs access, update compatibility and failure behaviour defined.
Two compatibility checks matter in particular. High-Performance Order Storage uses dedicated order tables; current WooCommerce guidance tells extension developers to use WooCommerce-specific order APIs rather than assuming order records can always be accessed through WordPress post APIs. The block-based Cart and Checkout also do not support every hook from classic shortcode checkout. Test the extension against the actual storage and checkout configurations, and document any unsupported combination.
Should you go headless with WordPress?
Headless means WordPress stays the editing back end while a separate front end fetches content through an API. A React, Next.js or Vue front end is a possible option, not an automatic performance result. Specify whether content uses WordPress REST routes or an additional GraphQL layer such as WPGraphQL, and check its current support and permissions.
Post previews, plugin-driven forms, SEO tags, navigation and other rendered output need explicit handling outside the normal theme. You also operate the CMS and the separate front end, with publishing, caching and deployment between them. Compare those responsibilities with a block-theme approach using the same real content and editor tasks.
What actually makes a WordPress site fast?
Profile what runs on each request with representative content and the selected plugins. Review repeated database queries, autoloaded options, asset loading, image delivery and cache behaviour. A plugin count alone is not a performance measurement. Select caching only after identifying which requests and users can safely share a result.
- Serve appropriately sized images and test the selected WebP or AVIF pipeline against required browsers.
- Load scripts and styles on the templates and journeys that need them.
- Move large imports and other long-running work out of an interactive page request.
- Evaluate Redis object caching and page caching through the chosen host, Nginx, Varnish or CDN.
- Use Query Monitor or another agreed profiler in a controlled, representative environment, and measure visitor-facing pages separately.
For a store or membership site, test logged-in sessions, carts, checkout, account pages and personalised content with caching enabled. An excellent anonymous homepage result does not establish that a returning customer sees the correct prices or account information.
How is a WordPress site kept secure after launch?
Security is ongoing risk reduction, not a perfect-security promise. Define the maintenance owner for WordPress, PHP, themes and plugins; install from trusted sources; remove unused extensions; restrict staff capabilities; and keep credentials out of theme files and repositories. Review administrator authentication, dashboard file editing and the hosting provider's responsibilities.
Updates need a staging and recovery plan, not indefinite delay. Keep consistent backups of files and database, retain them through an agreed secure process and prove that they can be restored. Record logging and incident escalation without claiming that monitoring prevents every compromise. A maintenance engagement needs its own scope and commercial terms.
Can you move an existing site to WordPress without losing rankings?
Plan the migration around content and URLs, but do not guarantee search rankings. Crawl the current site, map old URLs to intended destinations, preserve required titles, descriptions and structured data, and identify content being changed or intentionally removed. Import authors, media, dates and relationships with reconciliation checks rather than assuming a copied paragraph is a complete migration.
Prepare redirects, review canonical URLs and the sitemap, test the preview and agree cutover and rollback. Monitor the actual search and site-health evidence after launch with authorised account access. Search-engine decisions remain outside the development provider's control.
Presentation, domain logic and data have different jobs.
Custom theme and plugin separation
Presentation โ Domain โ Data is a useful review model. Templates render the interface. A plugin can register content types, implement business rules and own API endpoints. Agree the boundary for each feature so a visual redesign does not quietly disable content or require business logic to be copied into a new theme.
Keep feature folders and dependencies understandable. For a field-based content model, document where each custom post type and field group is registered, which templates consume it and which import or API process can change it. Separate repositories can be useful where the components have genuinely independent release cycles; they are not a guarantee that changes are risk-free.
Custom post types and API exposure
The WordPress reference documents register_post_type(), including the show_in_rest argument used for REST exposure and block-editor support. Register a post type on the appropriate lifecycle hook, use a distinct identifier and decide its rewrite, archive, capabilities and public visibility. Do not copy a public product-listing example into a sensitive record type.
Enabling REST support is not a complete integration or authorisation design. Test what an anonymous visitor, an editor and an administrator can read and change. Review metadata exposure, validation, sanitisation and custom endpoint permissions. A hidden admin menu is not proof that underlying records are private.
Scheduled and heavy work
Imports, exports and external synchronisation need work records, retry handling and operator visibility. WordPress documents that WP-Cron is triggered by page loads rather than running continuously like a system scheduler. A task due at a particular time may therefore run later if no page load occurs. Select an appropriate system-scheduler or queue design for time-sensitive work instead of assuming the word Cron supplies punctual execution.
Test a partial import, duplicate job, worker failure and downstream API outage. Record which system owns each record, what can be replayed safely and how to reconcile a missing update. Keep long-running work away from a customer-facing request where the result would otherwise depend on an open browser connection.
Environment and release boundaries
Use separate local, staging and production configurations, with approved deployment access and secrets stored outside source. A staging copy needs its own data-handling controls and should not send real customer messages or collect real payments during tests. Decide how databases, uploaded media and environment-specific URLs move between environments.
A production-like performance test should represent the PHP, database, caching and content conditions being evaluated. Debug or profiling tools can themselves affect results; control access, avoid exposing diagnostic output and record the method alongside the measurement.
Illustrative public-content registration
This small example belongs in an appropriate plugin, not a production theme edit. It demonstrates registration and REST/editor visibility for a public editorial content type. It does not implement private records, field validation, a WooCommerce product, order storage, custom permissions or a complete plugin lifecycle.
add_action('init', 'omnistu_register_case_type');
function omnistu_register_case_type() {
register_post_type('omnistu_case', array(
'label' => 'Case studies',
'public' => true,
'has_archive' => true,
'show_in_rest' => true,
'supports' => array('title', 'editor', 'thumbnail')
));
}
Review capabilities, public exposure, slugs, required fields, translation and activation/rewrite handling for the actual plugin. Do not use the public setting for sensitive records merely to make them appear in the editor.
Choose the engagement shape, then its responsibilities.
- Related catalogue platform: evaluate a separate application product, with WordPress only where explicitly part of its architecture.
- Custom WordPress build: agree theme, blocks, content types, custom plugins, content migration, store logic and integrations.
- Ongoing development and maintenance: agree capacity, patching, feature work, release approval, monitoring, recovery responsibilities and termination terms.
Choose the people, review cadence, milestone billing and support appropriate to the work. Confirm current availability and named responsibilities in the engagement terms.
Six acceptance areas for the delivery plan.
- Review: theme, plugin and configuration changes are traceable and reviewed according to an agreed release process.
- Testing: define repeatable checks for plugin logic, APIs and critical browser journeys such as login, forms and checkout.
- Profiling: measure representative content, selected plugins and production-like caching, with the test conditions recorded.
- Handover: specify source, history, dependency inventory, environment setup, REST routes, content model, deployment instructions, staff roles and a post-launch runbook. Transfer secrets through a separate approved secure route.
- SEO and presentation: check titles, canonical URLs, metadata, structured data, redirects, sitemap, images, browser support and accessibility. These checks do not promise a ranking or a certification.
- Operation: define uptime/error monitoring, alert ownership, restore evidence and any support terms. Logging is not a substitute for an incident response owner.
Check Chrome, Safari, Firefox and Edge on the devices agreed in scope. For a store, include payment, tax, shipping and refund scenarios. For membership or course content, include permissions and expiry. A green theme preview does not establish that every plugin integration works.
Technology options, matched to content and operation.
A brochure site and a large store need different operating decisions. Choose maintained, mutually supported versions at implementation time rather than treating an old minimum-version label as a current recommendation.
- WordPress / Gutenberg: CMS, block editor, templates and publishing workflow.
- PHP / MySQL or MariaDB: runtime and database, sized and maintained for the actual workload.
- WooCommerce: store responsibilities, with payment, inventory and extension compatibility reviewed.
- React / Next.js / Vue: possible separate front ends; WordPress REST or WPGraphQL as a separately selected content interface.
- Advanced Custom Fields: possible field and flexible-content tooling, subject to model and licence review.
- Yoast SEO or another selected SEO plugin: metadata controls that still need content and output checks.
- WP Rocket / Redis / Varnish / Nginx / CloudFront: alternative or complementary caching and delivery components; configure around personalised content.
- Git / Composer / WP-CLI: source control, dependency handling and repeatable administrative or migration tasks.
- Docker / AWS / WP Engine / GitHub Actions: packaging, hosting and deployment options, not an included hosting package.
- Sentry or another error-monitoring service: access, sensitive-data handling, retention and alert ownership need agreement.
- Firebase / Google Maps / Stripe / Razorpay / WebSockets / Node.js: optional external services or application components only when the workflow calls for them. Confirm current capabilities, merchant or account eligibility, cost and data flow.
From brief to handover, with dependencies visible.
- Brief and confidentiality: purpose, content types, editor roles, existing site and commercial boundaries. Agree any confidentiality terms before sharing sensitive materials.
- Scope and plan: theme or headless approach, plugins, store rules, migrations, integrations, environments and acceptance evidence.
- Build and review: version-controlled increments and a representative staging site; agree the review cadence and decision owners.
- QA and migration rehearsal: content and URL reconciliation, devices, accessibility, forms, access control, caching and external-service failures.
- Launch and handover: authorised release, redirects and DNS responsibilities, backup/rollback, documentation and receiving-team review.
Accounts, content readiness, vendor eligibility and external approvals can affect the plan. A ready-made application timeline is not a WordPress delivery promise. Launch and account changes require owner approval when executed.
What changes a WordPress estimate?
- Number of content types, relationships, field groups, blocks and page templates.
- Custom plugins versus selected third-party extensions and premium licences.
- WooCommerce catalogue size, variations, pricing, shipping, checkout and order workflows.
- ERP, CRM, payment or other service integrations and their exception handling.
- Multilingual content, translations, regional differences and multisite operation.
- Existing content volume, formatting, authors, media and URL migration.
- Headless preview, publishing, caching, deployment and hosting responsibilities.
- Testing, training, handover, monitoring, patching and restore requirements.
Compare one-time implementation with recurring hosting, extension licences and service costs. Agree scope, billing, change control and maintenance terms in a current written quote. No earlier example amount or duration is a current offer.
An illustrative large-catalogue store workflow.
Consider a retailer needing product import/export, ERP inventory sync, international prices, translated content and shipping rules based on weight and destination. This is an illustrative requirements set, not a claimed client deployment, product-count result, delivery record, uptime SLA or compliance certificate.
- Map source products, variants and media to the proposed store model, with repeatable imports and reconciliation.
- For a SAP or other ERP integration, identify the edition, supported interface, ownership of price and stock fields, and failure/replay behaviour.
- For zone-based shipping, define product weight, address validation, tax interactions and unsupported destinations.
- For a WPML or other translation/multicurrency approach, verify the selected extensions together and define which fields are translated or region-specific.
- If a multisite network is proposed, decide which content and configuration is shared and which sites have separate operational ownership.
- Rehearse updates and checkout using representative data; document performance and access results rather than inferring them from catalogue size.
- Agree the receiving team's source, configuration, training and operational evidence.
WordPress delivery review and handover.
Agree the implementation boundary, deliverables and acceptance checks in the project scope. Include the source and configuration to be handed over, third-party dependencies, account ownership and the receiving owner's installation and operating walkthrough. Review the selected work at the agreed milestones, with unresolved items recorded before release.
Proposed acceptance evidence includes a reproducible build, structured content examples, a tested editor journey, extension compatibility, a migration reconciliation report and a restore exercise. A repository alone is not proof that another team can operate the site.
Translate the sector into concrete requirements.
- Healthcare and life sciences: sensitive-data boundaries, booking and access requirements need an appropriate architecture and applicable expert review. No healthcare-compliance status is implied.
- Telemedicine: intake, consultation and provider workflows are separate from a marketing site and may need dedicated services.
- Fintech: onboarding, dashboards and payment flows require their own security, permissions and provider requirements.
- Retail and e-commerce: catalogue, cart, checkout, fulfilment and returns.
- Media and entertainment: content portals, access rights, subscriptions and any external streaming service.
- Creator economy: profiles, paywalls, memberships and entitlement changes.
- Transportation and mobility: booking, dispatch and location-related requirements, including any separate application backend.
- Food and beverage: ordering, menu availability, delivery zones and restaurant operations.
Questions to settle before work begins.
Do WordPress sites work well on phones and tablets?
Specify responsive layouts and the actual devices, content and journeys to be tested. A responsive theme is a starting point, not evidence that your finished pages work. A WordPress site is not a native app; if a separate app consumes its content, scope the API, authentication, app development and store-publication responsibilities separately.
How much does a build cost, and how long does it take?
Use the content model, theme or headless approach, plugins, migrations and integrations to prepare a written scope and estimate. A catalogue application is not a custom WordPress build. Agree dependencies, review decisions and the treatment of scope changes; there is no fixed amount or delivery date implied here.
Does the handover include the full source code?
List the custom theme, custom plugins, repositories, history, documentation and configuration to be delivered. Identify licence restrictions and account ownership. Have the receiving team follow the installation and release instructions using approved access. Source availability does not itself guarantee a frictionless handover or transfer every third-party right.
What hosting setup should be selected?
Compare managed WordPress hosting with an operated server against workload, region, access, backups, restore, monitoring and staging needs. Define PHP and database compatibility, object/page caching and CDN use for the real site. A large store and a small publishing site should not inherit an identical server specification without evidence.
Does SEO and performance work mean a ranking guarantee?
No. Scope metadata controls, XML sitemaps, schema, redirects, image handling, caching and performance checks explicitly. Keep the actual content and URL inventory reconciled, and distinguish technical checks from search-engine outcomes. DNS cutover and propagation also need planning, not a universal duration promise.
What happens after delivery if there are bugs?
Agree defects versus enhancements, patch responsibility, support hours if any, escalation and recovery. A maintenance retainer may cover updates and feature work, but its capacity, commercial terms and cancellation rules need their own agreement. No fixed support window is assumed.
How should NDA and confidentiality be handled?
Confirm the parties, purpose, permitted disclosures and handling of sensitive content or credentials before sharing it. Describe custom-work rights and third-party licences separately in the signed agreement.
Can custom WooCommerce plugins be included?
Yes as a scoped requirement: pricing, shipping, importers, subscription/B2B rules and ERP/CRM/inventory sync need their own design and tests. Do not edit core as a substitute for an extension. Check HPOS and the actual Cart/Checkout mode, and preserve those compatibility checks for future updates.
What distinguishes a custom build from a theme installation?
Review the proposed content model, blocks, theme and custom-plugin responsibilities. Ask which parts are original implementation, selected extensions or configuration, and how each is tested and handed over. A provider label or claimed office location does not answer those questions. Agree delivery contacts, timezone and response expectations directly.
Platform references used for technical checks.
Official documentation checked on 16 November 2026. Confirm supported versions and extension behaviour again for the actual implementation.
Bring the content model and the difficult workflow.
An editor who cannot publish safely, an importer that cannot be replayed, an extension that blocks updates or a store that behaves differently after caching are useful starting points. Define the operating problem and the evidence that would show it is fixed.
Discuss your WordPress scope โ