School website builder.
A school's website is the first thing a prospective family sees and the last thing most schools can edit themselves. YESS turns it into a section-based builder the front office runs without a developer: pick a theme, drop in pages, fill them with ready-made sections, and publish. And because the site lives inside the platform, its application form feeds admissions and its careers page feeds recruitment — the website is not a brochure, it is a front door.
- 19section types
- 8themes
- 4data tables
- ≈14 minto read
Prologue
Not a brochure, a front door#
Most school websites are built once by a contractor, handed over with a login nobody remembers, and frozen the day the contract ends. The term dates are wrong by October; the application form is a PDF download; and the only way to fix a typo is to email the agency and wait.
YESS rebuilds the school site as something the front office owns. It is a section-based builder — choose a theme, add pages, fill them with pre-made sections, edit the words, and publish — with no code and no developer. And because the site is part of the platform rather than bolted on, its forms do real work: a prospective parent who applies on the site lands in the admissions pipeline, and a teacher who applies to a vacancy lands in the recruitment dashboard.
The school's face to the world — edited by the school, wired to the school.
Chapter one
The builder#
The builder lives at /dashboard/website — a single page with three tabs: Pages, Theme, and Settings. Across the header sits the control that matters most: a Site Published master toggle, a strip showing the live URL, a Preview button, and a Live / Offline badge. Until the master toggle is on, the public site stays dark no matter what is built beneath it.
The work splits cleanly across the three tabs. Pages is where you build the structure and the content. Theme is where you set the look. Settings is where you handle the address, the search-engine metadata, and the domain. The chapters below take them in that order.
Chapter two
Pages and sections#
The Pages tab lists every page on the site — Home, About, Admissions, Contact — each with a publish toggle of its own. The first page becomes the home page at the root slug; the rest slugify from their titles. Opening a page splits the screen: the section list on the left, a live preview on the right.
A page is made of sections, and the catalogue offers nineteen types grouped by purpose — layout sections (hero, about, stats, features, programs, cta), media (gallery, video), social proof (testimonials, awards, staff, news, events), and conversion (admissions-steps, apply form, careers, faq, contact), plus a raw HTML section for anything bespoke. Most types offer several layout variants — a hero can be centred, split, cinematic, minimal, or an announcement bar — so the same content can wear a different shape.
Building a page is direct manipulation: Add section from the catalogue, reorder by dragging or with the up/down arrows, toggle a section's visibility, duplicate it, edit its content in a dialog, or delete it. For a fast start, the template picker offers ten complete starter sites — classic school, modern academy, faith-based, STEM focus, bilingual, admissions-focused and more — each of which populates a page with a full, designed set of sections in one click.
Chapter three
Theme and brand#
The Theme tab sets the site's whole visual character from a few choices. Pick one of eight themes — modern, classic, bold, warm, editorial, tech, organic, geometric — each pairing a heading and body typeface and a set of spacing, radius and shadow rules. Then set the colours: choose from twelve palette presets or dial in a custom primary and accent, pick a background surface from six options, and choose a text style (high-contrast, soft, or muted). The colour pickers autosave as you nudge them, and a live swatch shows the result.
The site's logo and brand colours default from the school's central branding, so the website matches the portal, the report cards and the ID cards without re-entering anything. The Settings tab links straight to /dashboard/settings when you want to change the brand at its source rather than just on the site.
Chapter four
Forms that do real work#
This is the chapter that separates a YESS site from a templated brochure. Two of the section types are not decoration — they are live front doors into the platform.
The apply form section lets a prospective family apply online. The programmes and academic years fill in from the school's own published data; on submit, the application is written into the admissions pipeline as a self-submitted application, admissions staff are notified, and the applicant is handed a reference and a token to track their status at /sites/[school]/application/[token]. The same form is always reachable at /sites/[school]/apply even before it is placed on a page.
The careers section lists the vacancies the school has flagged for the public website — only those that are published and within their deadline — and lets an external candidate apply inline with a cover letter, landing the application in the recruitment dashboard with a job reference. Its standalone home is /sites/[school]/careers. Both forms are fully translated across English, French and Arabic.
Chapter five
Address, search and domain#
The Settings tab handles how the world finds the site. You set the SEO meta title and description that show in a search result and a shared link, and you point a custom domain at the site. Two layers of publishing gate what goes live: each page has its own publish toggle, and the site has the master Site Published switch — a page appears publicly only when both are on.
On addresses, the platform serves each site from a subdomain of the YESS host — your-school.yourhost — routed automatically once the platform host and wildcard DNS are configured, with reserved names like www and app held back. A custom domain is stored on the school and recognised by the public site lookup; the last mile — pointing your own domain's DNS at the platform and mapping it at the edge — is an infrastructure step, and the Settings tab tells you the CNAME to set.
Chapter six
How the site renders#
The public site is served at /sites/[school]/[[...path]], resolved by the school's subdomain or custom domain. The platform reads the school's theme and palette into a set of CSS variables and the right web fonts, then renders each section by its type and layout variant into a styled page. The site wears a sticky navigation with the school's logo and a Portal Login button that drops a parent into the branded login for their school, and a footer.
Publishing is enforced at this boundary, not just in the UI. In production the public route shows a page only when the site is published, the page is published, and the section is visible; anything draft or hidden is withheld. (In a development preview, drafts render so the builder's own preview is faithful.)
Chapter seven
What makes the site elite#
Five things that make this elite
- 1
Forms wired to the platform
The application section feeds the admissions pipeline with notifications and a status-tracking link, the careers section feeds recruitment, and the contact section files every enquiry into the website Messages inbox. The website is a front door, not a brochure with a dead contact form.
- 2
Nineteen sections, ten templates
A catalogue of nineteen section types with layout variants, and ten complete starter sites that build a designed page in one click — so the front office assembles a real site without a designer.
- 3
Brand-synced by default
Logo and colours default from the school's central branding, so the site matches the portal, report cards and ID cards automatically — change the brand once and it flows everywhere.
- 4
Two-layer publishing
A page goes live only when both its own toggle and the site-wide master switch are on, and the public route enforces it server-side — so a half-built page can never leak before its time.
- 5
Multilingual front door
The public application and careers flows are fully translated across English, French and Arabic with right-to-left support, so a family applies in the language they read.
Planned features
What comes next#
The builder, the themes, the live application, careers and contact forms, and subdomain plus custom-domain serving all ship today. The items below are scaffolded or partial, and are flagged honestly so you can plan around them.
Four honest gaps
- 1
Custom domain, end to end
The app now serves any CNAMEd domain the school saves in Settings — the remaining step is attaching the domain and its TLS certificate at the hosting edge, which is still arranged outside the app. The planned upgrade automates that verification from the Settings tab.
- 2
Live staff and news sections
The staff and news section types are designed to auto-populate from the school's directory and announcements, but the public route does not yet feed them, so they render only manually-entered content. The planned upgrade bridges them to the live modules behind an explicit show-on-website consent flag.
- 3
Transactional reordering
Reordering sections saves each new position in a series of updates rather than one transaction. The planned upgrade moves reordering behind a single atomic call so a half-saved reorder can never occur.
- 4
Events and calendar bridge
The events section is manual today; the planned upgrade pulls term dates, holidays and public events straight from the school calendar so the site is never out of date.
Adjacent modules
Where the site connects#
The website is the public edge of several modules — it shows the school off and funnels strangers into the platform.
Adjacent modules
- 02Admissions & enrolmentThe apply-form section writes a self-submitted application into the admissions pipeline, with programmes and years pre-filled.
- 01CRM & lead pipelineA public enquiry on the site is the top of the funnel the CRM tracks from first touch to enrolment.
- 18HR & recruitmentThe careers section lists website-flagged vacancies and lands external applications in the recruitment dashboard.
- 27Platform foundationBranding feeds the site's logo and colours; the Portal Login button hands visitors to the school's branded sign-in.
Tutorial
Do it step by step#
Publish a real school site with a working application form in six steps — theme, pages, sections, forms, settings, and the master switch.
- 1
Set the look
Open the Theme tab of /dashboard/website, pick a theme, choose a palette preset (or a custom primary and accent), a surface, and a text style. The logo and brand colours default from your school branding.Start from a theme that matches the school's character — editorial for a traditional school, tech for a STEM academy — then adjust the palette.
- 2
Build the pages
On the Pages tab, add Home, About, Admissions and Contact. The first page becomes the home page; the others slugify from their titles. - 3
Fill them with sections
Open a page and add sections from the catalogue — a hero, an about block, programmes, stats — or apply a starter template to lay out a whole page at once. Reorder with the arrows and edit each section's words in its dialog.Applying a starter template replaces the page's sections, so use it on an empty page and then edit, not over hand-built content.
- 4
Add the application form
Drop an apply form section onto the Admissions page. It pulls your programmes and academic years automatically, and every submission lands in the admissions pipeline with a tracking link at /sites/[school]/apply. - 5
Set address and SEO
On the Settings tab, write the SEO meta title and description, and — if you have one — enter your custom domain and note the CNAME to set. The subdomain address works without any DNS. - 6
Publish
Toggle each page you want public to published, then flip the master Site Published switch in the header. Use Preview to walk the live site at /sites/[school]/[[...path]] before you announce it.
Themed, built, wired to admissions, and published from one screen — the school's front door is open, and the front office holds the key.