How to Build a School Website Without Writing Code
To build a school website without code, start from the page map rather than the design: admissions, staff, calendar, news, and contact. Describe those pages, their content, and who updates them. An AI builder generates the site in a few minutes, publishes it to a real address, and later pages get added by describing them.
A school site serves three audiences at once: prospective parents deciding whether to apply, current parents looking for a date or a form, and staff who have to keep it current. Designing for all three is what makes this different from a business website.
What pages does a school website actually need?
Schools accumulate pages. Twelve years later there are ninety of them and four say something about uniforms. Start with the set that gets used, and add only when someone asks twice.
- Admissions. Entry requirements, key dates, fees if you charge them, and one obvious way to start an application. For an independent school this is the page that pays for the site.
- Calendar and term dates. The most-visited page in most school sites by a wide margin, because parents check it constantly and lose the emailed PDF.
- News and letters. Where the head's letters and the trip announcements live, so parents have somewhere to look instead of asking the office.
- Staff and departments. Names, roles, and how to contact the right person. Cuts more phone calls than any other page.
- Contact and practical details. Address, map, office hours, absence reporting line, and how to reach the school in an emergency.
Everything else is optional at launch. A curriculum page per subject is worth building once the core is live and someone owns keeping it accurate.
What should the prompt say?
The builder needs the structure and the tone. Schools are the one category where an over-designed site actively hurts: parents want to find a date on a phone in ten seconds.
Build a website for [school name], a [primary / secondary /
independent] school in [city] for ages [range].
Pages: Home, About, Admissions, Curriculum, Staff, News,
Calendar, Contact.
Home: hero photo, one-line mission, three key facts
[pupil numbers, founded, inspection rating], quick links to
Admissions, Term dates and News, plus the latest 3 news items.
Admissions: process in numbered steps, key dates table,
fees table if applicable, and an enquiry form with
[parent name, child age, entry year, email, message].
Calendar: term dates table by term, plus a list of events.
Staff: photo, name, role, and department for each person.
Contact: address, map, phone, absence line, office hours.
Style: clean and warm, high contrast, large readable type,
works on an older phone. Accessible colour contrast throughout.
Two lines earn their place. Asking for accessible contrast explicitly matters because a school audience includes grandparents and assistive technology users, and it is far cheaper to ask for it up front than to fix it later. And the quick links on the home page, because three of the four most common visits are people trying to leave the home page immediately.
Which build size fits your school?
A nursery and a secondary school need very different sites. The table compares the three sizes and what each one implies in credits and upkeep.
| Size | Fits | What it costs |
|---|---|---|
| One page, everything on it | Nursery, small private tutor centre, a school in its first year | A quick build at 6 credits, and it stops working around eight sections |
| Core multi-page site | Most primary schools | A platform build: 12 credits for the first three pages, 3 for each page after |
| Multi-page site plus a parent area | Schools that need logins, documents, or per-year content | The platform build plus a database and auth, which is a project rather than an evening |
Most schools belong in the middle row and should stay there. The third row is where student data appears, and that changes the nature of the work entirely, as the last section explains.
How does news get published without a developer?
This is the question that decides whether the site is alive in two years. There are two honest answers, and they suit different schools.
Editing by description. Adding a news post in Zugo means writing what it says: "add a news item dated 12 September titled Year 6 residential, two paragraphs about the trip and the deadline for consent forms." Each edit costs 3 credits and is re-checked before it goes live. This is fine for a school posting a few times a term and terrible for one posting daily.
Storing posts in a database. Connect Supabase and the news page reads from a table, so publishing becomes adding a row rather than editing the site. This is the right shape for a school with an office administrator who posts weekly. The connection is covered in the guide to building an AI app with Supabase.
Whichever you choose, decide who owns it before launch. The most common failure of school websites is not technical, it is that nobody was named as the person who updates term dates.
How do forms and enquiries reach the office?
An admissions enquiry form that silently discards submissions is the worst possible failure for this site, because the parent believes they applied. Connect Resend and every submission arrives as an email in the office inbox.
Two refinements are worth the edits. Send a copy to a second address, so a single person's holiday does not swallow a fortnight of enquiries. And add an automatic reply confirming receipt with a realistic response time, which cuts the follow-up phone calls that otherwise arrive two days later.
For absence reporting, resist the temptation to build a form at all. A tappable phone number and a clearly stated email address work on every device, need no maintenance, and cannot break on a Monday morning when forty parents use them at once.
One rule holds for every form on a school site: ask for the least you can act on. An admissions enquiry needs a name, a contact address, and the child's entry year. Date of birth, current school, and a paragraph about educational values can wait for the conversation, and each extra field measurably reduces the number of parents who finish.
Test the whole path before term starts. Submit the form yourself, confirm the email arrives in the office inbox rather than a spam folder, and check that whoever answers it knows the site now sends them things.
What does a school site cost to run?
A core multi-page site is a platform build: 12 credits for the first three pages and 3 credits for each additional page. Zugo's free tier gives 5 starter credits, Pro is $25 per month with 200 credits, and Business is $99 per month. Hi-Fi mode doubles the cost of a build or an edit and is rarely necessary for this category.
Every build is booted in a sandbox before you see it, and one that fails to render is reported as a failure rather than delivered as working. That lowers the risk of a term dates page breaking the week before September, though it does not remove it, so check the live site after any edit that matters.
The code belongs to the school. GitHub export produces a normal repository and Vercel deploys to your own account, which matters for an institution that expects the site to outlast whoever built it. A related guide on the multi-page question in general is can AI make a multi-page site, and the smaller-scale version of this build is covered in the guide to a language school website.
When does a school need more than a website builder?
Honest limits, and for schools they are unusually important.
Student data. Grades, attendance, safeguarding records, and anything identifying a child sits under data protection law with real penalties. This is not a place for a site built in an evening and never reviewed. Specific requirements like retention rules and access logging get built through careful work with a developer, not one prompt.
Integration with a school information system. If registers, reports, and parent accounts already live in an MIS, the website should link to it rather than duplicate it.
Formal accessibility compliance. Many schools are legally required to meet a published accessibility standard and to publish a statement. A generated site can be built with good contrast and structure, but a compliance audit is a separate piece of work with a signature at the end of it.
Payments for fees. Stripe connects for payments, and that covers trips and clubs well. Full fee billing with instalments and sibling discounts is finance software.
For a school that needs a clear, current, fast public site and does not need to run a parent portal through it, this is an evening rather than a procurement cycle. You can write the first prompt at zugo.dev.