Book a demo

middleschool.site · The public website builder for middle schools

The public site your middle school actually needs -- bell schedule, clubs, and announcements a family can find.

A family looking up tomorrow’s bell schedule, a club’s tryout dates, or an early-dismissal notice should find your school’s OWN public page for it -- not a login-walled portal and not a photo of a flyer taped to the front door. Middle School Sites is the tool your office uses to build that page itself: ordered pages, a real nav, and a typed content palette -- a calendar embed for the bell schedule and day pattern, a card grid for clubs and athletics, a staff directory, a news feed and an alert banner for announcements, and a document list for forms and policies -- all in the free core.

Book a conversation Why a site, not another portal →

This builder is in active development. No school is running a live public middleschool.site build yet, and money is honest-off -- there is no live charge on this page. A Pro tier for extra pages and advanced modules is off by default.

Five pages, free, no gate everThe core site -- create it, build up to a five-page cap, and use the whole core block palette -- runs with no paywall, ever. Editing an existing page, within or over that cap, is never gated either.
A broken page cannot publishAn accessibility check runs on every save and blocks publish outright if it finds a problem -- alt text, contrast, heading order, link names, video captions. Not a scan after the page is already live.
Every student photo, re-checked on every readA photo's consent is re-verified on every single public page load, not just once at authoring time. A revoked consent drops the photo on the very next read.
Adult-authored, alwaysA student or minor is denied at creating or editing a school website, every time. An adviser, co-adviser, or admin runs the site; a student can appear in consent-gated content, never own the surface.

Why a site-building tool, not another single-purpose portal

The middle grades are the one stage where nobody has published the public page yet

Three things make a real, self-published site the right shape for a middle school -- not a nice-to-have layered on top of the program, publications, and roster tools the platform already runs.

A public school needs its own front door

A family searching for a bell schedule, a club roster, a permission-slip form, or an early-dismissal notice expects to find the school’s OWN public page for it -- not a login-walled portal, and not a scan of a printed flyer. None of the platform’s other middle-grades surfaces publish that public, multi-page site: the daily-glance reader shows one family a snapshot inside the platform, the roster-sync technology produces a single branded page as one artifact of a much bigger job, and the staff hub and the office bundle both face inward. This is the surface that IS the public site.

The palette matches how a school office already communicates

The content blocks are the same things an office already keeps: a printed bell schedule taped by the door, a club sign-up sheet, a memo posted at the front desk, a binder of forms. A calendar embed, a card grid, a staff directory, a news feed, an alert banner, and a document list turn those into pages a family can actually search for and bookmark -- the same information, in a form a search engine and a phone browser can reach.

Free does not mean thin, and compliance is never the upsell

The core site -- five pages and the whole core block palette, including the exact set the school needs for a bell schedule, clubs, staff, and announcements -- is free and unpaywallable. The accessibility gate applies at every tier; it is never something a Pro upgrade unlocks. Pro only gates GROWTH -- more pages, more advanced modules -- never the baseline promise or the compliance floor.

What the builder does

Six capabilities, all traced to the shipped website-builder code

Every capability below is real, shipped code on the platform’s school-website builder -- this page describes what it does for a middle school, it does not invent a new engine.

Pages built from a typed content palette, not raw HTML

A site owns ordered pages, and each page is an ordered doc of typed content blocks -- hero, heading, text, image, gallery, a call to action, and the school-data blocks below -- with its own place in the nav and a draft-to-published status. There is no HTML to hand-edit and no template to fight; an office builds a page by adding and ordering blocks, and a page only goes public once it is explicitly published. An unknown or malformed block is refused at the parser, never silently rendered.

Built & wired

Bell schedule, clubs and athletics, staff directory, and announcements -- all in the free core

A calendar embed carries the bell schedule and day-pattern data; a card grid lays out clubs and athletics; a staff directory resolves the school's own staff list; a news feed points at the school's already-public newsroom edition; an alert banner covers an early dismissal or a closure notice; and a document list surfaces board policies, forms, and notices by category. Every one of those is in the CORE block palette -- the free floor -- alongside a five-page cap that costs nothing to reach and is never gated on an existing page.

Built · free core, unpaywallable

A page cannot go live broken -- an accessibility gate blocks publish

Every page save and every publish runs a fail-closed accessibility check: image alt text, color-contrast math on any author-chosen colors, heading levels that never skip downward, no empty headings, a discernible name on every link and call to action, and captions on any authored video. A finding blocks the save with the full list so the fix is obvious, and blocks publish outright until it is resolved -- this is checked at the authoring boundary, not scanned after the page is already public.

Built · fail-closed at publish

A Pro tier exists for growing past five pages and the advanced modules -- off by default

Beyond the five-page core cap and the core block palette, an above-floor Pro tier adds more pages and an advanced module set -- FAQ accordions, tabbed panels, video embeds, an events feed, testimonial cards, social embeds, a lead-capture form, and a custom grid layout. Pro is a real, code-level entitlement, but it is seeded OFF for every plan and carries no live price: it fails closed until we turn it on for a school. Nothing above the core floor is available on this page today, and there is no checkout anywhere on it.

Built · off by default · money honest-off

A school website is adult-authored -- never a minor's own surface

Creating or editing a school website is denied to a student or minor every time, at creation and at every later edit. Only a district or school admin, or an adviser or co-adviser, can own or author the site. A student can still appear inside the site's content -- a consent-gated testimonial, a photo in a gallery -- the same way any student can appear in any of the school's other published material, but a student never runs the authoring surface itself.

Built · adult-authored · fail-closed

What Middle School Sites is -- and what it hands off

Middle School Sites is the public website-building tool itself: the pages, the block palette, the nav, and the publish flow a middle school office actually authors. It is not the program a middle school runs, not the publications editor a student staff writes in, not the roster-sync technology underneath, not the staff-facing group hub, not the front-office bundle, and not the family daily-glance reader -- those are six separate, already-bespoke surfaces on the same platform, and this page cross-links each rather than re-describing it.

Concretely: middleschool.software is the program front door a student and family use directly -- electives, scheduling, clubs, counselor supports. middleschool.press is the publications editor a student staff runs the yearbook and newspaper in. middleschool.technology is the roster-sync technology that keeps the directory, ID cards, and every activity page current as the roster turns over. middleschool.center is the staff hub an advisory teacher or counselor reads their group from. middleschool.services bundles records, a directory, publications, and communication into one front-office managed service. middleschool.today is the family's daily-glance reader of what today looks like. middleschool.site is none of those -- it is the tool that builds and publishes the school's own public, multi-page website, the front door the public actually lands on.

A family’s visit, in one public page each

A parent lands on the school’s own site the night before a half day, sees the early-dismissal notice in the alert banner at the top, checks tomorrow’s bell-schedule pattern in the calendar embed, browses the athletics card grid for tryout dates, looks up their student’s homeroom teacher in the staff directory, and downloads a field-trip permission form from the document list -- all without an account, all on ONE public site the office itself built and keeps current. Every block is a pointer resolved on the server at the moment the page is served, so nothing sits baked into the page as stale copy the office has to remember to update by hand.

If that page ever included a student’s photo -- a club picture in a gallery, a quote in a testimonial -- the same consent recheck runs on this visit as on every other: only a photo that currently clears publication for every student pictured is served, and a suppressed student’s name and image are simply absent. Nothing here replaces the picture-day product, the publications editor, or the roster-sync layer; it reads the same underlying records and presents them as the school’s own public pages.

A public site is still a records surface -- handled that way

Publishing a page to the open internet raises the stakes on student privacy, not lowers them. A school website is the one surface on the platform allowed to carry a student’s photo or name at all, and every public read runs a fail-closed consent recheck rather than trusting whatever was true when the page was authored. A student never owns or edits the site -- authoring is denied to a minor at creation and at every mutation, every time.

Facial recognition is off by default, and any photo the site shows is found by matching the school’s own roster, never by scanning a face. A minor’s photo is never made public, never indexed by a search engine, and never sold; sharing it is consent-gated and can be withdrawn at any time, and a withdrawal takes effect on the very next page load. A picture-day print order, where a school runs one, is fulfilled through a vetted outside print lab -- not every step of that separate product stays fully in-house -- and we never sell student data. The honest, keepable posture is the narrower one: consent-gated, off by default, and rechecked on every visit, not a claim that nothing about a student ever exists in the system.

What is built and what is honest-off — plainly

The page builder, the free core, the accessibility gate, and the consent recheck are built. Pro and money are honest-off.

Built and wired today: the typed-block page builder with ordered nav and a draft-to-published lifecycle; the free, unpaywallable core (a five-page cap, never gated on an existing page, and the whole core block palette -- calendar, card grid, staff directory, news feed, alert banner, document list, and contact); the fail-closed accessibility gate that blocks publish, not just a warning; the unconditional consent recheck on every public read of a page that carries a student's photo; and the adult-only authoring gate that denies a minor at creation and at every edit.

Honest-off: the Pro tier (extra pages past the core cap, and the advanced module set) is seeded OFF for every plan and carries no live price -- it fails closed until we enable it for a school. Money is honest-off across this page: no live billing, no subscription, no live payment, no live checkout. No school is running a live public middleschool.site build yet -- a conversation is the honest next step. Middle School Sites is FOR-PROFIT software for middle schools; it is not itself a school, a district, or a nonprofit. Nothing here is legal advice.

FAQ

Common questions

How is middleschool.site different from the other middleschool.* surfaces?

Each is a distinct surface on the same platform. middleschool.software is the program front door a student and family use directly. middleschool.press is the publications editor a student staff writes in. middleschool.technology is the roster-sync technology underneath. middleschool.center is the staff hub. middleschool.services bundles records, directory, publications, and communication for the front office. middleschool.today is the family's daily glance. middleschool.site is the tool that builds and publishes the school's own public, multi-page website -- the front door the public actually reaches.

Do we need to write HTML or hire a designer to build a page?

No. A page is built from typed content blocks -- a hero, a heading, text, an image, a calendar embed, a card grid, a staff directory, a news feed, an alert banner, a document list, a contact card -- ordered and saved through the builder, not hand-coded. A page only becomes public once it is explicitly published.

Is the free core really free forever, or is it a trial?

It is free, unpaywallable, and not a trial: creating a site, building up to a five-page cap, and using the whole core block palette carry no gate at any point. Editing an existing page never gates on the cap either -- only adding a NEW page beyond five, or using an advanced Pro-only block, touches the Pro entitlement, and Pro itself is off by default with no live price today.

What happens if a page fails the accessibility check?

Saving a page that fails returns the full list of findings so the fix is clear, and the draft still persists -- no work is lost. Publishing is different: a page with any outstanding finding is hard-refused from going live. The check covers image alt text, color contrast, heading order, empty headings, discernible link names, and video captions.

Can our site show a photo of a student?

Only through a consent-gated block -- a gallery or a testimonial -- and only for a student whose photo currently clears publication. That check runs again on every single public page load, not just once when the page was authored, so a parent's revoked consent removes the photo on the very next visit. Facial recognition is off by default, and a minor's photo is never made public, indexed, or sold.

Can a student run our school's website?

No. Creating or editing a school website is denied to a student or minor every time -- only a district or school admin, or an adviser or co-adviser, can own or author it. A student can still appear inside the site's content the same way they might in any published school material, just never as the person running the authoring surface.

What does Pro add, and what does it cost?

Pro is an above-floor entitlement for pages beyond the five-page core cap and an advanced module set -- FAQ accordions, tabbed panels, video embeds, an events feed, testimonial cards, social embeds, a lead-capture form, and a custom grid layout. It is a real, code-level tier, but it is seeded off for every plan and carries no live price today; it fails closed until we turn it on for a school. There is no checkout on this page.

How do we get started?

By a conversation, not a signup. Middle School Sites is in active development, and no school is running a live public build on middleschool.site yet. A conversation walks through what is built, what is honest-off, and what Pro would add, plainly. Email [email protected].

Give your school the public page it should already have

Bell schedule, clubs and athletics, staff directory, and announcements -- built from a free core block palette, published only when accessible, and rechecked for consent on every visit. The builder is in active development, and a conversation walks through what is built, what is honest-off, and what Pro would add, honestly. Money is honest-off; there is no live charge on this page.

Book a conversation See the program front door →