Why small website changes take so long at many schools, and how a simple editor lets your own staff publish news, vacancies and fees.
Small changes, long waits
Most of what changes on a school website is small: a news story, a job vacancy, a new member of staff, next year's fees. Each one matters to someone reading the site that week.
When every edit has to go through a developer or a complicated platform, those small updates pile up. The site falls behind the school, and parents notice the old dates and missing faces.
What staff actually need to change
Ask the admissions or marketing team what they update most, and the list is short.
It usually looks like this
News and blog posts about events and school life
Job vacancies that open and close through the year
Staff profiles with photos, names and roles
Fee tables that change every school year
An editor built around those few jobs is easier to learn than a platform that tries to do everything.
Simple beats powerful
Big website platforms give staff hundreds of settings. Most people use a handful and are nervous about the rest.
A good school editor shows a form with only the fields that matter: a title, a photo, the text, a date.
Staff fill it in and press publish.
The page keeps the school's design, because the design is not something they can break.
Publishing without asking for help
With our staff editor at /editor, school staff sign in, make the change and publish it in one click. There is no code to touch and no ticket to send to an agency.
The update goes live on the site.
What we built it to handle:
Posts with photos, for news and the blog
Vacancies added and removed as jobs open and close
Staff profiles kept current as people join or leave
Fees tables updated for the new school year
Everything else on the site stays as it is until you ask us to change it.
Where the care plan fits in
Bigger changes, like a new page, a new section or a rework of the admissions area, still come to us. They are part of the yearly care plan.
Staff handle the weekly updates. We handle the structure, the hosting and anything technical.
The editor works for as long as the school's yearly plan is active.
Before you choose an editor
Ask who on your team will actually use it, and what they change most often. Then ask to see that exact task done, start to finish, on a real page.
If it takes more than a few minutes to explain, it is too complicated. The test is simple:
Can the person who knows the news publish it themselves?
