CMS development
A site your own team can edit without a developer.
- Editable pages
- Media library
- Roles and approvals
- Training and handover
What this is for
A site whose words and pictures change more often than its design does. A content-managed build separates the two: the structure and the layout are fixed, and the content inside them is yours to change whenever you like. That is worth doing when updates are frequent enough that waiting on a developer would slow them down. It is worth skipping when a site changes once a year, because a system nobody uses still has to be maintained.
What it covers
- Editable pages
Each page is assembled from defined blocks rather than a free-form editor, so somebody editing text cannot accidentally break the layout around it.
- Media library
One place for images and documents, with sizes and formats generated on upload, so a photograph straight off a camera does not slow the page down.
- Roles and approvals
Who may edit, who may publish, and who may only draft. Not everybody who needs to change something needs the ability to put it live.
- Training and handover
A session with the people who will actually edit, on the real site, and a written reference for whoever joins after them.
What you end up with
- Pages your own team edits
Text, images and page order changed without a developer and without a deployment.
- A media library that stays organised
Uploads are resized and converted on the way in, so the library does not degrade into a folder of unlabelled files.
- Roles, so not everybody can publish
Drafting and publishing are separate permissions, and who holds each of them is yours to change later.
- A training session for the people editing
Run with the people doing the work, rather than only with whoever commissioned it.
What we need from you
- Who edits, and who approves
They are often different people, and where that line sits shapes how the system is set up.
- The pages that change most often
Those are the ones worth making editable first. Parts that never change are cheaper and safer left fixed.
- Any existing content, as it stands
Moving what exists across is part of the work, and it is far easier to plan for when it can be seen early.
Who works on it
Each part is done by the specialist for it, in the order the work reaches them.
How it runs
- DiscoveryFirst
We work out what you need, what it has to do, and what it will cost.
- Scope written down
- Fixed quote
- Agreed timeline
- DesignBefore the build
You see the site before it is built, on desktop and phone, and approve it before the build starts.
- Designs to approve
- Mobile and desktop
- Final copy
- BuildThe build
The design is built to its measurements, on a link you can open at any point during the build.
- Live preview link
- Progress you can see
- Content loaded
- LaunchHandover
Domain, hosting and email pointed at the new site. Checked on real devices, handed over in your name.
- Live on your domain
- Accounts in your name
- Support after launch
- SupportAfter launch
Updates, fixes and changes for as long as the site is live.
- Updates and fixes
- Monitoring
- A number to message
Questions people ask first
With a conversation about what you actually need, and then a written scope with a price against it. Nothing is built until you have agreed both, and that scope is what the work is measured against for the rest of it.
Also under Build
Get in touch
Every one of these reaches us directly, and is answered by a person.