A web studio for schools, for deciding parents and looking-something-up parents.
An education website serves two completely different visits. One person is choosing between three schools; the other needs next week’s calendar in forty seconds on a phone. Most sites are built for the first and fail the second, or the reverse. Norml designs and builds the structure that handles both — and hands it to staff who are not web people.
A few clients we’ve worked with
What we do
School website design for the two people who actually use it — a prospective parent deciding, and a current parent looking something up — with a site your own staff can keep current.
The admissions story is beautiful and the term dates are three clicks deep.
- A prospective parent and a current parent land on the same homepage, and it is optimised for whichever of them the last redesign cared about.
- The calendar, the newsletter and the lunch menu live in three different systems, none of which matches the site.
- Staff and department pages were filled in once at launch and have been wrong since the second staff change.
- Curriculum pages read like a policy document, because they were pasted from one.
- Everything goes through one person in the office who knows how to log in, and when that person is out nothing gets published.
What a website has to carry for an institution.
Schools and institutions publish constantly, to families, students and staff, through people whose job is not the website.
- 01Staff keep it current
A publishing system built around the people who actually post means term dates and notices are right because updating them is easy.
- 02Families find things under pressure
Most visits are someone looking for one specific thing quickly. Structure matters more here than almost anywhere.
- 03Enrolment has a clear path
Prospective families following an admissions route should never have to guess what the next step is.
What our education web design services include.
Seven things, in the order we do them. Website design for schools is mostly about separating the two visits and making the site survivable by staff who have a day job.
- Separating admissions from day-to-dayThe first architectural decision. Which pages persuade a family choosing a school, which pages serve a family already in it, and where they meet. Everything downstream follows, and almost no institutional site does it deliberately.01
- A page per programme, year group or departmentRather than one Curriculum page covering everything. That is also how the pages get found: a parent searches for the programme, the year group or the subject, not for the institution they have not heard of yet.02
- The admissions pathEnquiry, open-day booking, application — designed as one journey with tracking at each step, so you can see where families stop rather than guessing. Where an existing application system is in place, we route into it rather than replacing it.03
- The practical layer, taken seriouslyCalendar, term dates, newsletters, policies, staff contacts and closures — the pages that get the most traffic and the least design attention. Fast, findable, and correct on a phone at 7am.04
- Design system in FigmaComponents, states and responsive rules, so the tenth department page looks like the first and a new staff member does not need a designer.05
- A build the office can actually runStructured so a department head or an office administrator publishes a newsletter or updates a staff list alone. The Farm Soho runs a 500-plus page content system this way, managed by an editor with no developer on call, and AstraZeneca is the same problem at enterprise scale.06
- Accessibility and analyticsAccessibility treated as a build requirement rather than an audit you fail later — publicly funded and public-facing institutions get held to it — plus Search Console, analytics and admissions conversion configured at launch.07
What clients say.
“We didn’t choose them to be impressed — we chose them because we knew they’d deliver high-level results with no risk. As a CTO myself, that’s exactly what I look for in a long-term partnership.”
“And, you know, the great part about the fact that you hit the goal, it's not that you had to compromise anything that you were doing, because, honestly, the end result far exceeded what we could have imagined.”
“I would just say that you deliver on quality … I just thought we clicked, and you delivered what we were looking for.”
“Norml Studio's professionalism and responsiveness were impressive.”
School website design deliverables.
The scope follows the size of the institution and how many departments publish. A typical engagement hands over the following:
- A page map covering every URL, which visit it serves, and what it has to prove.01
- A Figma design system with components, states and responsive rules.02
- Programme, department, staff, news and policy page templates.03
- An admissions path designed end to end, with tracking at each step.04
- A build your office and department staff update without a developer.05
- A publishing workflow that works when the one person who knows it is away.06
- Analytics and Search Console configured, with admissions conversion tracked.07
- A handover session and every account and file in your name.08
Our process
How the work runs.
- [Discovery]Step 01
We read the analytics and follow both visits through the current site — a family choosing, and a family looking something up. The traffic usually says something different from what the last redesign assumed.
- [Architecture]Step 02
The split between admissions and day-to-day, the page map and the URL plan, agreed in writing before anything is designed.
- [Design]Step 03
Wireframes first, then the system in Figma. Programme, department and news templates, not a stack of static screens.
- [Build]Step 04
The site and the publishing workflow behind it, built for staff rather than for developers.
- [Launch and handover]Step 05
Redirects, analytics, Search Console, speed, then training for the people who will actually publish.
The people who do this work.
Meet the whole teamNo account layer between you and them. These are the Norml specialists this work runs through.
From the Norml blog.
Let's chat
“I've spent 10 years working across development and marketing. I started as a developer, but design, SEO and advertising were already part of the job. That taught me to treat a website as one system: the business, the content, the design and the code have to work together. At Norml, I lead the architecture behind our work and stay involved wherever strategy, design, development and search meet.”
Max TymoshynFounder & Architect
Get startedSchool and education web design questions.
Have you built a website for a school or university?
No, and this is the thinnest proof of any industry we publish, so we will be blunt about it. The work shown here is from other sectors, chosen for the mechanics an institution needs: a 500-plus page content system run by one in-house editor, a content-heavy site rebuilt without losing its traffic, and a platform built so a large organisation could publish at pace without engineering in the loop. Everything on this page is either a technique from one of those published projects or ordinary design practice. If an education portfolio is what you are buying, several school website design companies specialise in exactly that and will show you one.
What does an education web design agency actually change?
Usually the architecture and the publishing workflow, not the visuals. Almost every institutional site tries to serve a deciding parent and a current parent with one structure, and almost every one routes publishing through a single person in the office. Splitting the first and distributing the second is most of the improvement — the redesign people notice is the smaller half.
Can you connect to our student information or application system?
Usually yes, and the aim is to route into what you already run rather than replace it. The integration pattern is the same one we build for any system of record — conditional forms adapting to the enquiry, routed with the right owner and immediate notification, which is what we built for Metroplex Homebuyers. Which system you use changes the work, not whether it is possible.
Do you handle accessibility compliance?
We build to WCAG 2.1 AA as standard — semantic structure, keyboard operation, contrast, focus states, real alternative text and accessible documents. What we do not do is certify you. A formal audit by an accessibility specialist is a separate exercise, and an institution should budget for one; building it in first makes that audit cheap rather than a rebuild.
Our staff are not web people. Will it fall apart?
That is the design constraint from the first day rather than a promise at the end. Templates instead of free-form pages, so a department head cannot accidentally break a layout; a workflow that does not depend on one person; and training at handover for the people who will actually publish, not for whoever attends the meeting.
We are a university, not a school. Same approach?
Same method, much larger governance. Higher education website design adds faculties publishing independently, research output, international recruitment and a great many stakeholders — so the design system and the permissions model carry more weight than the page designs do. The two-visit split still holds; it just becomes several.
How much does school website design cost?
Norml publishes its rates on Clutch — $50–$99 per hour with a $5,000 project minimum. A full engagement covering architecture, design system, templates and build sits well above that minimum. We scope after discovery, because the page count follows the departments and programmes. For a small school on a tight budget, a specialist education platform may genuinely be the better buy, and we will say so.
What happens after launch?
Your staff run it — that is what the handover and the training are for. When an institution would rather not, Norml Care covers updates, monitoring and small changes monthly.
Building or rebuilding a school website?
Website 2.0 combines strategy, design, development and launch in one engagement, with the publishing workflow treated as part of the build rather than an afterthought.