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-day
The 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.
A page per programme, year group or department
Rather 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.
The admissions path
Enquiry, 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.
The practical layer, taken seriously
Calendar, 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.
Design system in Figma
Components, states and responsive rules, so the tenth department page looks like the first and a new staff member does not need a designer.
A build the office can actually run
Structured 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.
Accessibility and analytics
Accessibility 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.