CMS Development
Make publishing and maintaining your content easier with an organised editing experience.
- WordPress
- Drupal
- Headless CMS
- Next.js
Overview
A content management system is what lets your team change the website without a developer. This service covers the structure behind that: how content is modelled, who can edit and publish it, and how it reaches the site.
For a straightforward business website, that usually means WordPress — covered in detail under WordPress Website Development. This service is for the cases that need more: a headless setup feeding several front-ends, a custom editorial workflow, or content shared between a site and an app.
Problems this solves
- Content is duplicated by hand across pages and platforms
- Anyone with access can publish anything
- The content structure cannot express what the business sells
- Editors avoid the admin area because it is confusing
Who this service suits
- Teams with several editors and a real approval process
- Businesses publishing the same content to a website and an app
- Organisations with structured content such as products, courses or listings
- Companies outgrowing a page-builder site
Features and deliverables
Content structure
- Content models for your real content types
- Taxonomies, categories and relationships
- Media library organisation
- Reusable content blocks and templates
Workflow and access
- Editing workflows with draft, review and publish states
- Roles and publishing permissions
- Scheduled publishing where needed
- Editor training and handover documentation
Delivery
- WordPress, Drupal or a custom CMS, chosen to fit the scope
- Headless CMS with an API-driven front-end
- Migration of existing content
- Search and listing pages driven by the content model
Technologies we use
The final stack is chosen per project, based on scope, budget, who will maintain the site and what it needs to connect to. Not every technology listed is used on every project.
Platforms
- WordPress
- The usual choice for business and content websites, with a familiar admin area.
- Drupal
- Used where structured content and fine-grained permissions matter more than simplicity.
- Headless CMS
- Content kept in one place and delivered by API to a website, an app or both.
Front-end
- React.js and Next.js
- Build the public site that reads from a headless CMS.
- PHP
- The language behind WordPress and Drupal, used for custom modules and templates.
How a project runs
The same stages apply to every project. Which of them are included, and how long each takes, is set out in your proposal.
- 01
Requirement Discussion
We go through what you need, who it is for and which features matter most, so the scope is built on your actual priorities.
- 02
Scope and Proposal
You receive a written proposal setting out the deliverables, assumptions, timeline and cost before any work begins.
- 03
UI/UX and Planning
Structure, screens and user journeys are designed and agreed, along with the technical approach for the build.
- 04
Development
The approved scope is built in stages, with the work shared as it progresses rather than only at the end.
- 05
Testing and Quality Assurance
Functionality, responsiveness, performance and content are checked across devices and common browsers.
- 06
Client Review
You review the build against the agreed scope and raise changes, which are handled before deployment.
- 07
Deployment and Handover
The project goes live on your hosting or platform account, with access, credentials and a walkthrough handed over.
- 08
Post-Launch Support
Where support is included in the agreement, the covered period and scope are stated in the proposal.
Timeline
A delivery estimate is given in the written proposal, once the scope is agreed. Estimates are not delivery guarantees: the date moves with the scope and with how quickly reviews and content come back.
What affects the timeline
- The number of pages, screens or modules in the agreed scope
- How quickly content, images and brand assets are provided
- Review and approval turnaround at each stage
- Third-party dependencies such as payment gateways, APIs or platform approvals
How pricing works
This service is quoted per project. Tell us what you need and we will come back with a written proposal covering scope, deliverables, timeline and cost.
A project quotation is separate from the monthly care plans, which cover ongoing changes after launch.
Add-ons and what is not included
Optional add-ons
Quoted separately, on top of the agreed scope.
- Content migration beyond the agreed volume
- Multi-language and localisation setup
- Custom editor plugins or modules
- Editorial training sessions
- Ongoing maintenance through a care plan
Third-party costs and exclusions
Paid directly to the provider, or outside the project scope.
- Hosting, CDN and CMS subscription costs
- Paid plugin, module and theme licences
- Content writing and editing
- GST, where applicable, is charged additionally
Start a project enquiry
Let’s talk about your
CMS Development project.
CMS Development is already selected below. Send a few details and we will come back with next steps and a written proposal — you don’t need a technical brief to start.
- What you want to build or improve
- The tools or systems you already use
- Your timeline and budget, if known