CMS website development: a site your team updates itself
CMS website development gives your company a website your own team can edit: new pages, news, job ads, case studies and product updates published in minutes, without waiting for a web agency. We build on WordPress, Drupal or a headless CMS, chosen for how you publish, with a content structure that keeps the site consistent as it grows, an editor experience your staff will actually use, and every old address carried over when you move. The site, the content and the hosting account are yours.
- You see the result before it goes live
- Fixed price for the agreed scope, in writing before work starts
- Source code, domain and accounts in your company's name
Looking for a content management software company? We do not sell a CMS of our own. We choose an established CMS for your case, then build, migrate and run the site on it, so your content is never tied to a product only we maintain.
When a CMS is the right choice
A content management system pays off when content changes often and several people change it. If marketing posts news every week, HR publishes job ads, sales updates references and product pages change with the range, each of those people should be able to do it themselves, with the design and the structure held in place by the system. That is what a CMS is for.
When a site changes a few times a year, a static site is often better: faster, lighter to run and with nothing to patch, and we make the edits. Our website development page compares the kinds of site. For portals where customers or partners log in, see website portal development, and for online shops, online store development.
Choosing the CMS
WordPress is by far the most common choice. W3Techs' content management survey (read 11 November 2026) reports that WordPress is used by 39.3% of all websites, a 58.0% share of the sites whose CMS it can identify, with Shopify, Wix and Squarespace next, and 32.2% of websites using none of the systems it monitors. Being common is an advantage: more people know it, more integrations exist, and your site is never dependent on one supplier. It is not automatically the right answer.
| Type | Examples | Fits when | Watch out for |
|---|---|---|---|
| Traditional open-source CMS | WordPress, Drupal | Company sites, blogs and news, multilingual sites, sites with many editors | Core and plugin updates; too many plugins slow the site and widen the attack surface |
| Headless CMS | Strapi, Payload, Sanity, Contentful | Content used on a website and in an app or other channels; sites where speed and design freedom matter most | A separate front end to build and maintain; preview needs setting up |
| Hosted site builder | Wix, Squarespace, Webflow | Small sites with standard needs and no integrations | Limits on structure, integrations and moving away later |
| Commerce platform | Shopify, WooCommerce | Sites where the shop is the main purpose | Content features are secondary to the shop |
We recommend from your requirements: how many editors, how many languages, which systems the site must connect to, how often content changes, and who will maintain it in three years. The reasons go into the written scope, so the choice can be checked later.
Content modelling: the part that decides the next five years
The most important work in CMS website development is invisible to visitors. A content model defines the kinds of content the site has, such as service pages, case studies, people, offices, job ads and news, and the fields each one carries: title, summary, body, image with alt text, related services, location, dates. With a model, the design stays consistent no matter who publishes, lists and filters build themselves, and content can be reused in several places without copying.
Without a model, every page is a blank canvas, and after two years the site has twelve kinds of heading, five button styles and pages nobody can find. We design the model with your editors before any template is built, using your real content rather than placeholder text, and build the editing screens around it: the fields an editor needs, in the order they think, with help text and limits where a mistake would break a layout.
Editors, roles and workflow
- Roles. Authors write, editors approve and publish, administrators change settings. Each person gets only the rights their work needs.
- Drafts, preview and scheduling. Content is written as a draft, previewed exactly as it will appear on desktop and phone, and published now or at a set time.
- Revisions. Every change is kept, so a mistake is undone in one step and you can see who changed what.
- Languages. For multilingual sites, each page is linked to its translations, with the right language tags for search engines, and editors see which translations are missing.
- Media. Images are resized and compressed automatically, with required alt text, so the site stays fast and accessible whoever uploads.
- Sign-in. Editor accounts use strong sign-in, single sign-on with your Microsoft or Google accounts where available, and are removed when people leave.
We also train your editors on the finished site, with a short written guide for the tasks they do most.
Accessibility and search built into the templates
A CMS makes it easy to publish, which also makes it easy to publish badly. We put the rules into the templates rather than relying on every editor: headings in the right order, alt text required for images, readable contrast, forms with clear labels and error messages, and pages that work with a keyboard and screen readers. We build to WCAG 2.2 level AA. If the site sells products or services to consumers, the European Accessibility Act applies to it as an e-commerce service for services provided after 28 June 2025 (Directive (EU) 2019/882, read 11 November 2026).
Search engine basics are in the templates too: editable titles and descriptions, clean addresses, a sitemap that updates itself, structured data where it fits, and fast pages. See SEO for the work beyond that.
Moving from an old CMS
Many sites run on a CMS that is out of date or out of support. Drupal is a clear example: Drupal 7 security support ended on 5 January 2025, and the project states that it no longer receives security updates or compatibility updates (Drupal.org, read 11 November 2026). A site on an unsupported version is a security risk that grows every month, and moving it is the fix.
- Inventory. Every page, post, file and address on the old site, with its traffic and inbound links, so nothing valuable is lost.
- Map to the new model. Old content types are mapped to the new content model; content that no longer earns its place is retired on purpose.
- Move. Content, images and files are moved by script where possible, then checked by people.
- Redirect. Every old address either stays the same or gets a permanent redirect to its new address.
- Check and switch. The new site is compared with the old one page by page, then switched over, and search console and analytics are watched in the weeks after.
Our website redesign page covers the design side of a move and how rankings are kept.
Hosting, updates and security
A CMS is software that needs looking after. The core, the theme and every plugin get updates, some of them security fixes, and a site left alone for a year is a common way in for attackers. We keep plugins to the ones that earn their place, host in an EU region as standard, run daily backups that are restored in tests, and monitor uptime. Our WordPress maintenance covers this for a fixed monthly fee, or your own IT team takes it over with our documentation. For what a CMS site costs to build and run, see the website development cost guide.
How the project runs
- Brief. Your goals, your editors, your content and the systems the site connects to.
- Scope and fixed price in writing. The CMS and why, the content model, templates, integrations, migration and what is left out.
- Design and content model. Designed with your real content, approved before building.
- Build in rounds. A working site on a test address that your editors try from the first round.
- Launch and training. Migration, redirects, switch-over, editor training, then monitoring.
You own it
As a standard term, the code, the content, the domain and the hosting account belong to your company, and an open-source CMS carries no licence that ties you to us. You can keep us for maintenance or move the site to another team at any time. See prices.
Questions we get
What is CMS website development?
Building a website on a content management system, so your own team can create and edit pages, news, products or job ads in a browser without touching code. The work covers choosing the CMS, designing the content structure, building the templates and editor experience, moving existing content, and setting up hosting, updates and backups.
Which CMS is best: WordPress, Drupal or a headless CMS?
It depends on how you publish. WordPress suits most company sites and blogs and has the largest pool of people and plugins. Drupal suits large, structured sites with complex permissions. A headless CMS suits content that feeds several channels, such as a website and an app, or a site where speed and security matter most. Hosted builders suit very small sites with no custom needs.
What is a headless CMS?
A CMS that stores and manages content but does not render the website itself. The content is delivered through an API to a separate front end, which can be a website, an app or a screen in a shop. It gives full design freedom and speed, at the price of building and maintaining that front end.
Can you move our site from an old CMS?
Yes. We export the content, map it to the new content model, move images and files, keep or redirect every old address so search rankings carry over, and check the result page by page before switching. Sites on platforms that no longer receive security updates, such as Drupal 7, should move first.
Who maintains the CMS after launch?
You choose. Your team edits content; the CMS core, plugins and hosting need regular updates and tested backups, which we can handle under WordPress maintenance or a maintenance agreement, or hand over to your own IT team with documentation.
Do we own the website and the content?
Yes. The code, the content, the domain and the hosting account are your company's, and an open-source CMS has no licence that ties you to us. You can keep us for maintenance or move the site to another team at any time.
Get a written quote
Tell us in a few lines what you need. We reply within one working day with a written quote: scope, timeline and a fixed price or an hour estimate. Asking is free and commits you to nothing.