"Can we edit it ourselves?" comes up on nearly every website call we have.
It usually comes from experience. A marketing lead at one credit union described their previous vendor this way:
It takes them a very long time, sometimes weeks, to make an editor update, and they charge a crazy amount of money.
A marketing manager at a public software company put it more bluntly:
So I don't have to keep coming back to you for every little damn change.
Both are fair. If your staff have to call a developer to change a date on the events page, something is wrong with the setup. But "can we edit it" is too broad a question to get a useful answer. Every CMS vendor will say yes, and every demo will show someone changing a headline. What you need to know is which changes your staff can make, safely, without training they will have forgotten in three months.
"Edit" Means Six Different Things
Break the question apart. Staff editing usually covers some mix of these, in rough order of difficulty:
- Text and images on existing pages. Correcting a phone number, swapping a photo, updating a bio.
- Structured content. Adding an event, a news post, a staff member, a job listing, a resource. Items that follow a set format.
- New pages from existing templates. A new program page that looks like the other program pages.
- Navigation and menus. Adding the new page to the menu, reordering sections.
- Forms. Adding a field, changing where submissions go.
- Layout and design. A new kind of page, a different arrangement of sections, a new color or component.
Most organizations need the first four to be self-serve, want the fifth to be possible, and are better off not doing the sixth themselves. Know which of these your team actually needs before the demo, and ask to see those specifically.
Content Versus Structure
The most useful principle in this whole decision: staff should own the content, and the structure should be protected.
Content is what you say: the words, images, events, and pages. Structure is how the site works: templates, layouts, the design system, and the code underneath. When staff can change content freely but cannot accidentally break structure, you get both freedom and stability.
We say this to clients in almost these words: you typically don't want so much control that someone can go in, click one thing, and everything breaks. A CMS that lets anyone change anything is not more flexible. It is more fragile. The page that looked right on launch day slowly drifts, fonts multiply, and eventually the site needs a redesign just to look consistent again.
The best setups give editors a set of well-designed building blocks they can arrange and fill, with the design decisions already made.
The Test That Beats Any Demo
Do not let the vendor drive. Ask for a test account, or a screen share where your person has the controls, and have the least technical person who will actually edit the site try five real tasks:
- Change the text and image in one section of an existing page.
- Add an upcoming event with a date, location, and registration link.
- Create a new page from an existing template and add it to the menu.
- Replace a PDF that is linked from three different pages.
- Undo a change they made by mistake.
Time it. Watch where they hesitate. If it takes a guided walkthrough to complete, it will take a support request once the walkthrough is forgotten.
Questions to Ask
Can We Undo?
Revision history is the difference between confident editors and nervous ones. Ask whether every page keeps previous versions and whether an editor can restore one without calling anyone.
Can We Preview and Schedule?
Staff should be able to see a change before it goes live, and schedule content to publish or unpublish at a set time. Event pages that expire on their own save a surprising amount of cleanup.
Can We Control Who Edits What?
In most organizations, several people edit different parts of the site. Roles and permissions let the events coordinator manage events without being able to change the homepage.
What Can't We Change, and Why?
This question gets the most honest answers. A good vendor will tell you exactly where the line between content and structure sits and explain the reasoning. A vague answer usually means the line has not been thought about, which usually means it is in the wrong place.
Who Fixes It When Something Breaks?
Editors will occasionally break something. What happens next? Is there someone to call, and is that included or billed by the hour?
The Honest Part About Platforms
Which CMS matters less than how it is set up. A well-configured site on almost any mainstream platform can give staff comfortable control of content. A poorly configured one on the best platform in the world will send every change back to a developer.
If your site is mostly publishing, like articles, news, and resources, WordPress is often a sensible choice, and we recommend it when it fits. When the site behaves more like an application, with member data, integrations, and custom workflows, a platform built for that kind of structure will be easier to edit safely over time. Either way, ask to see your own real tasks done on the real setup you will get, not the vendor's showcase.
Editing Yourself Is a Choice, Not a Requirement
One more thing worth separating: being able to edit the site yourself is not the same as wanting to.
Some teams enjoy owning their content and have someone with time to do it. Others would rather send a note and have it handled. Both are reasonable, and the right answer can change year to year as staff and priorities change.
That is why our own Managed Website plans keep the site identical and differ only in how content changes are handled. On every plan your staff can edit pages, sections, and media themselves. What changes is whether you want us to handle changes quoted one at a time, batched on a quarterly cycle, or without limit. Make sure whatever you choose gives you both options, so you are not locked into doing it all yourselves or doing none of it.
A Simple Rule of Thumb
If routine content changes require a developer, the CMS is set up wrong. If anyone can change the design, it is set up dangerously.
The right setup sits in between: content is yours, structure is protected, and there is someone to call either way.
Final Thoughts
"Can our staff edit it?" is really three questions: which changes, by whom, and with what safety net. Get specific answers to each, test them with your own people on your own tasks, and you will know more than any feature list can tell you.
The goal is not maximum control. It is enough control that your team never waits on a developer for something they should be able to do in five minutes.
If your team is stuck waiting on someone else to change your own website, we can show you what a well-structured setup looks like. See our Managed Website plans, or book a short consult.