CMS websites
CMS website development
A content management system (CMS) lets people without coding skills add and update a website's content. CMS website development is the work of choosing a suitable system, structuring content within it, building templates that display that content, configuring how editors work and setting up hosting and maintenance. The choice of system matters less than how well it fits your content, your team and your budget over several years. Starting with the content and the people who will edit it, rather than with a favourite platform, leads to better decisions.
This page explains what a CMS does, the main approaches, how to model content, editor workflows, choosing a platform and what to plan for after launch. LetGetGrow builds, redesigns and maintains WordPress and Webflow websites, with the scope, cost and timeline of each project set out in a custom quotation.
Illustrative diagram
CMS approaches
- Self-hosted
- Your hosting
- Your updates
- Full access
- Hosted
- Provider runs it
- Plans
- Limits
- Headless
- Content store
- Separate front end
- More development
What a CMS does
A CMS separates content from design. Editors fill in forms or a visual editor; templates turn that content into pages with consistent styling. A good CMS setup lets the right people publish quickly, keeps pages consistent, controls who can change what and makes it straightforward to add new content types as the business grows.
Main CMS approaches
| Approach | How it works | Consider |
|---|---|---|
| Self-hosted | Software you install on your own hosting | You manage updates, security and hosting |
| Hosted platform | The provider runs the software and hosting | Plan limits, export options, recurring fees |
| Headless | Content stored in a CMS, displayed by a separate front end | More development, more flexibility |
| Static with a CMS layer | Pages built ahead of time from CMS content | Fast and secure; publishing triggers a rebuild |
Model content before choosing
List the kinds of content you publish, the fields each has, how they relate and where they appear. A site of a few static pages has different needs from one with hundreds of articles, products or locations. The content model shows which features a CMS must have and helps compare platforms fairly.
Think about the editors
Who will publish, how often, and with what skills? Do some people need to draft while others approve? Should editors control layouts, or only fill in content within fixed templates? Testing a shortlisted CMS with the people who will use it day to day can be more revealing than any feature list.
How a CMS project runs
Requirements
Content, editors, integrations, budget.
Output: Requirements list
Platform choice
Shortlist compared and tested.
Output: Chosen CMS
Content model and design
Types, fields, templates.
Output: Approved model and designs
Build and content
Templates built, content entered.
Output: Complete staging site
Launch and handover
Training, maintenance plan.
Output: Live site and guides
Example: choosing a CMS for a regional theatre
Illustrative example — not a client case study
Situation: A theatre publishes shows, performance dates, news and education resources, edited by several staff.
- The content model links each show to many performance dates and education resources.
- Two platforms are shortlisted and tested by the marketing and education teams.
- The chosen CMS supports draft-and-approve workflows the theatre needs.
What this shows: Staff could publish shows and dates consistently. This example is illustrative.
Before choosing a CMS
Content
- Content types and fields listed
- Volume estimated for two years
People
- Editors and roles identified
- Approval steps defined
Running costs
- Hosting or plan fees known
- Maintenance owner named
Total cost of ownership
Compare platforms over several years: build cost, hosting or plan fees, licences, maintenance effort, editor time and the cost of moving away later. A platform that is cheap to start can be expensive to run, and the reverse.
Getting content out later
Ask how content can be exported if you change platform. Self-hosted systems can give full access to the database; hosted platforms vary. Check current export options before committing.
Maintenance and security
Self-hosted systems need updates, backups and monitoring. Hosted platforms handle much of that but limit control. Either way, decide who looks after the site, how backups work and how editors' accounts are managed.
Integrations
List the tools the site must connect to, such as a CRM, newsletter, booking system or shop, and check how each platform supports them before choosing.
Accessibility
Check that templates produce accessible pages and that the editor encourages good practice, such as alt text and proper headings.
Planning for growth
Consider where the site will be in two or three years: more content types, more editors, more languages or an online shop. A CMS that handles today's needs but not likely next steps may force a costly move later. Equally, choosing a complex system for a simple site adds cost without benefit.
Questions about CMS website development
What is a CMS?
Software that lets people update website content without coding.
What are the main CMS approaches?
Self-hosted, hosted, headless and static with a CMS layer.
How do we choose a CMS?
Start with content, editors, integrations and running costs.
What is a headless CMS?
A CMS that stores content while a separate front end displays it.
Can we move platforms later?
Check each platform's export options before committing.
Who maintains a CMS site?
Decide in advance; self-hosted systems need regular updates.
Request a Custom Quote
Ask about CMS website development
Thank you — your enquiry has been sent.
We have received your message and will reply by email. If you need to add anything, email info@letgetgrow.com.