Services Development
CMS websites
Websites your own team can edit and publish, without waiting for a developer.
At a glance
- Includes
- Page models, roles, previews, publishing workflow and editor guidance
- Works with
- Your brand, content and design files
- Delivered as
- A published website with a content system and code in your repositories
- Starts with
- A review of your content and who will edit it
Fit
Is this right for you?
Usually the right call when one of these sounds familiar.
Every change needs a developer
Small edits wait days for someone with access.
Content lives in many places
Pages, files and copy are scattered and out of date.
Several people publish
You need roles, review and a clear approval step.
A site that no one dares touch
A change on one page can break another.
Not the right service? A shop with checkout and orders: E-commerce. Mostly a tool with accounts and data: Web apps.
Scope
Scope and what you get
Each piece of work has a matching thing you receive.
- What we do
Content models
We agree with your editors the page types, fields and reusable sections.
What you receiveA content structure
Page types your editors understand and a clear list of what each contains.
- What we do
Build and design
Pages built from the sections your editors will actually use, matching your design.
What you receiveA published website
A site that looks as designed and stays consistent as pages are added.
- What we do
Roles and publishing
Roles, drafts, previews and an approval step for those who need one.
What you receiveA workflow that fits
Editors, reviewers and publishers set up with the access each needs.
- What we do
Editor guidance
Short written guides for the jobs your team does most often.
What you receiveConfidence to edit
Guidance written for your team, in plain language.
Use cases
Relevant use cases
Practical situations where this service is put to work. Open a card to see how it applies.
A company site your team can run
A site where marketing and operations update pages themselves.
- Page sections editors can reorder
- Previews before anything goes live
- Roles for editors and approvers
Replacing a site no one can edit
A rebuilt site with the content moved across and a cleaner way to manage it.
- Existing content reviewed and brought over
- Redirects planned for old addresses
- Editors trained on the new system
A site with several contributors
A publishing workflow for teams where more than one person writes.
- Drafts and review before publishing
- Roles for authors and reviewers
- A record of who changed what
Sample use cases, drafted as placeholders. The Plethora team confirms the final list.
Process
How it works
Each stage is agreed with you as we go. Each shows what we do and what we need from you.
Understand
We doWe review your content, your editors and what the site needs to do.
You doYou share existing content and introduce the people who will edit.
Model
We doWe agree the page types, fields and sections with your editors.
You doYour editors review the models and tell us what is missing.
Build
We doWe build the site and the editing screens, loading content as we go.
You doYou try the editor, add real content and give feedback.
Launch
We doWe prepare the launch, run through the editor guide and hand over the code.
You doYou approve the launch and decide what support you want afterwards.
Quality
Quality and handover
How the work is checked, accepted and passed to you.
Tried by your editors
Your team edits real pages during the build, not only at the end.
Previews before publishing
Changes can be checked before they are visible to visitors.
Access by role
Editors see and change only what their role allows.
Written editor guidance
Short guides for the tasks your team does most.
Tools
Tools and technology
Tools we use in delivery. We choose them to suit your team, and the list does not imply any partnership. Logos belong to their owners.
- WordPress
- React
- Next.js
- TypeScript
- PostgreSQL
- Docker
Engagement
Engagement and cost factors
Ways to work with us
A scoped project
A defined website, built and handed over.
A team alongside yours
Our engineers work with your team on the site.
Ongoing support
Updates, fixes and small changes after launch.
What shapes scope, timing and cost
- Number of page types and sections
- Amount of content to bring across
- Roles and approval steps needed
- Languages the site must support
- Connections to other tools
- How much support you want after launch
Scope and cost are confirmed with you in writing before work starts.
FAQ
Frequently asked questions
We recommend from your team, content and plans, and explain the choice. Both are options.
Yes. That is the aim, and the guides cover how to do it.
Usually. We review it first and agree what to bring across and what to rewrite.
You do. Code, content and accounts are delivered to you.
Get a website your team can run. Start with a conversation.
Tell us what you want to build and we will come back with next steps.
Talk to usRelated