bloomz 
A district website fails in two directions, and most fail in both. It falls out of date because nobody has time to maintain it, so the calendar still shows last year’s events and the staff directory lists people who left. And it carries legal risk, because the accessibility work that the law requires is hard to do and easy to skip. Both problems trace back to the same root: the website is treated as a separate system from the daily work of running a district, maintained by different people on a different schedule with a different budget.
This guide is about choosing a website platform that does not drift and does not expose you. It covers accessibility as a legal floor, the hidden cost of running the site apart from your communication, what total cost actually includes, and how to migrate without surrendering a semester to the project. The goal is a public site that stays current because keeping it current is a byproduct of work you were already doing.
What districts actually need from a website
Strip away the marketing and a school or district site has a short list of jobs. It is the front door for prospective families. It is the system of record for calendars, bell schedules, staff directories, and policies. It is where the public, the press, and the board go for official information. And in an emergency it has to hold up under traffic and tell people the truth quickly.
Those jobs share a requirement that pretty templates do not satisfy: the information has to be right, today, without a webmaster manually updating it. A beautiful site with a stale calendar is worse than a plain one that is accurate, because families learn they cannot trust it and stop checking.
Accessibility is a legal floor, not a feature
WCAG and ADA compliance is not a nice-to-have you get to eventually. Some districts have learned that through complaints and lawsuits. Public school websites are expected to meet WCAG accessibility standards, and updated ADA Title II rules have made that expectation concrete for state and local government entities, including school districts. A site that fails on color contrast, missing alt text, unlabeled forms, or keyboard navigation is a liability sitting in public view.
The trap is that accessibility is not a one-time audit. Every new page, every uploaded PDF, every event a staff member posts can reintroduce a violation. So the platform itself has to carry the load: accessible templates, enforced alt text, structure that screen readers can navigate, and guardrails that keep a well-meaning staff member from publishing an inaccessible page. Evaluate accessibility as an ongoing property of the platform, not a checkbox someone ticked at launch.
The duplicate-entry problem, and the one-engine fix
Here is the failure that drives most stale district sites. The website lives on one system and family communication lives on another. A teacher posts a field trip to the app, and the same information has to be re-entered on the public calendar by someone else, later, if at all. Multiply that across every school, every announcement, and every event, and the public site falls behind within weeks. Nobody decided to let it rot. The duplicate entry just lost to everything more urgent.
The fix is structural. When the website and the communication platform run on the same engine, posting happens once. A staff member shares an announcement or an event, and it appears both to families in the app and on the public site, governed by who is allowed to see it. The public calendar stays current because it is the same calendar, not a copy someone maintains by hand. This is the core idea behind Bloomz Slick Sites: the site runs on the same engine as the communication, so the act of communicating keeps the website alive.
Keeping the public-private boundary clean
One engine raises an obvious question: how do you keep private student information off the public page? The answer has to be built in, not left to staff discipline. Audience and visibility belong to the post itself. A classroom update goes to enrolled families. A district announcement goes public. A grade goes to one guardian and never appears anywhere else. When the platform enforces that boundary by design and is FERPA and COPPA compliant, “post once” is safe. When it is not, shared-engine convenience becomes a way to leak. Make that boundary a thing you test, not a thing you assume.
Total cost, including what gets cut
Website platforms in this market are often priced per site, with hosting, an SSL certificate, accessibility add-ons, and support sold separately. The sticker price is rarely the real number. Add it up across every school in a district and the total can be substantial, especially when each building runs its own contract.
The larger savings, though, comes from not buying the website as a separate product at all. A district that runs its site on the same platform as its communication is not paying a second vendor, a second hosting bill, and a second support contract for a system that duplicates data from the first. Bloomz publishes transparent pricing from $3 per student per year with the platform free for parents, and the website capability is part of that rather than a separate line. When you compare, compare the whole bill: the website vendor, the hosting, the accessibility tooling, and the staff time spent keeping two systems in sync.
Migration without the six-month project
The reason districts stay on a website they dislike is the fear of moving. A migration that means rebuilding every page by hand, re-uploading every document, and retraining every staff member is a project nobody volunteers for. But a migration does not have to look like that. With structured content import, a sensible default site that is accessible out of the box, and editing simple enough that the people who post to families can also post to the site, a move can be measured in weeks. We lay out exactly how to approach it in migrating a district website without the six-month project. The short version is that the migration effort is a question to ask the vendor directly, because the answer varies enormously and it determines whether you ever actually switch.
How to evaluate platforms
A few questions surface the differences fast:
- Does the platform enforce WCAG accessibility on every new page, or only at launch?
- Does posting once update both the public site and family communication, or is it duplicate entry?
- Is the public-private boundary enforced by the platform, and is it FERPA and COPPA compliant?
- What is the total cost including hosting, SSL, accessibility, and support, across every school?
- Can non-technical staff keep the site current, or does everything route through a webmaster?
- How long does migration take, and who does the work?
A district website should be the easiest thing to keep accurate, not the hardest, because the information on it is information you are already sharing every day. The platforms that get this right collapse the website and the communication into one act. The ones that do not leave you maintaining two systems and trusting the public one less every month. Bring your current site and the pages you know are out of date. Schedule a demo and we will show you what one engine looks like in practice.