Public school website pages

Create and publish custom pages on the public site, follow the draft to published workflow, and know which switch makes the whole site visible.

School website guide for day and boarding schools.

Last updated August 29, 2026

The public site is a set of fixed routes plus whatever custom pages you add. Fixed routes such as about, academics, admissions, contact, facilities, faqs, policies, and downloads always exist and pull their content from the matching CMS collection. A custom page is a WebsitePage record with a slug, title, body, and optional SEO title and description, reachable at that slug under the public site.

Pages can be written as plain body content or built from the same section blocks the homepage uses. When a page carries blocks it renders with the builder layout; when it does not, the body is used. That is the practical difference between a quick policy page and a designed landing page for admissions.

The workflow

Status	Public?	Who can set it
DRAFT	No	Any CMS user
IN_REVIEW	No	Any CMS user, to hand the page to a reviewer
SCHEDULED	Once the time passes	Publishers only
PUBLISHED	Yes	Publishers only

Before you publish anything

School profile complete - name, address, phone, email - because the public layout renders it in the header and footer
Brand colours, fonts, and logo set in school settings, since the public theme reads them directly
Navigation and footer links configured, otherwise the defaults are used
A verified custom domain if you do not want the site served on the default path

Handoff

The public site is where prospective families meet the school before they have an account, so its main handoff is into admissions. An admissions page should send readers to the public application form rather than describing the process in prose, and the contact form should be treated as a lead queue that someone in the office actually works. Everything else on the site - events, staff directory, gallery, downloads - is pulled from its own CMS collection and published on its own schedule.

Limits

One site per school. There is no multi-language version and no per-page access control
Revisions are stored, but there is no visual diff or one-click restore in the editor
The contact form writes into an enquiries inbox in the admin app; it does not create an admission application

Common questions

Quick answers in plain language.

I published a page but the public site shows nothing.+

The site configuration itself has to be published as well. Every public route checks that first, so an unpublished site returns nothing regardless of how many pages are marked published underneath it.

Who can publish, and who can only edit?+

Platform Admin, Principal, and office Admin act as publishers - they can publish and schedule. Vice Principal is an editor, able to edit and review but blocked with 403 when trying to publish or schedule. Everyone else has no CMS access at all.

How does scheduled publishing work?+

A publisher sets a future date and the page is stored as SCHEDULED and not published. Public queries treat a scheduled page whose time has passed as visible, so it appears on its own without needing a cron job.

Can two pages share a slug?+

Not within one school. The slug is unique per school, so an existing about page has to be renamed or removed before a second one can take that address.