Book a demo

elementaryschool.website · For elementary schools · One roster, one public site

A fuller school website for elementary schools — newsletters, a staff directory, translated family pages, and event sign-ups, all off one roster.

A small elementary office should not need a web team, or a second stack of tools, just to keep families informed. This page is the public-facing site: a family newsletter families opt into themselves, a staff directory drawn from the same roster the office already runs, a translated version of a staff message for a family's home language, and event sign-ups decided by a fail-closed consent-and-capacity rule. It is a for-profit product FOR elementary schools — not a school itself. Money is honest-off; a conversation is the honest next step.

The newsletter and the staff directory are built and wired today. Translated family pages are consent-gated by design and honest-off today — no live translation runs from this page yet. Event sign-ups are decided by a built consent-and-capacity engine; the live registration store and the event-day extras are in early access.

Opt-in, not roster scrapingA family subscribes itself with a double opt-in — a subscriber row is never derived from the roster.
One staff roster, one directoryThe public staff directory is the same roster the office already manages, not a second list to keep in sync.
Consent before a seatAn event sign-up needs an explicit granted consent; a missing or unclear answer is always a no, never a default yes.
Honest about what is not live yetTranslated family pages are honest-off today; the sign-up store and event-day extras are early access. This page says so plainly.

What is built

Four capabilities, off one roster

Each capability below is labelled honestly. “Built” means the engine is production-ready today; where a piece is consent-gated-but-not-live or early access, the label says so.

A family newsletter, opt-in only

A family subscribes itself — a double opt-in, never an automatic add from the roster. An adviser or editor composes an issue from the school's own already-published stories and sends it to confirmed subscribers only; every issue carries a one-click unsubscribe link that is always honored.

Built & wired

A public staff directory, off the same roster

The office already manages a staff roster in the platform — name and role, admin-managed. This page's directory is that same roster presented publicly: a name, a role, and a school-chosen contact, never more than the school chooses to publish.

Built

Translated family pages, consent-gated

The design is a consent-and-notice-gated lane for translating a staff message into a family's home language, built with exactly one transport in mind rather than a public translation service. Today it is honest-off: no engine is wired here yet, so no live translation runs from this page.

Consent-gated · honest-off today

Event sign-ups, decided fail-closed

A staff member creates the event; a sign-up is confirmed only with an explicit granted consent, and capacity is enforced exactly — a full event waitlists rather than overbooking. That decision rule is built; the live registration store, notifications, and event-day extras are in early access.

Decision engine built · rest early access

The newsletter — a family opts in, an adviser sends

A family reaches the subscribe form and provides an email; that lands a pending row and a confirm link goes out. Only once the family clicks that link does the subscription become confirmed and mailable. There is no roster scraping — a subscriber row is created ONLY by that explicit opt-in, never derived from the class roster or the family directory, so a newsletter list is never a back door into the roster.

An adviser or editor composes an issue from the school's own already-published stories — the same stories families can read on the school's online edition — and sends it to confirmed subscribers only. Every issue carries a one-click unsubscribe link, and an unsubscribe is always honored: the row flips and is never mailed again. Delivery itself is honest about its own state: a real send goes out when the school has a mail connection configured, and a graceful no-send otherwise — never a faked “sent” confirmation.

The staff directory — one roster, presented publicly

An elementary office does not want to keep a staff list in two places: one for the internal roster and a second, hand-updated page for families. Here there is one roster. The school's admin already manages its staff — who is on staff and what role they hold — inside the platform, with every change audited. The public directory on this site reads from that same roster, so a name or a role corrected once is correct everywhere it appears.

What a family sees is deliberately modest: a name, a role, and a school-chosen contact — never more than the school decides to publish, and never a home address or a personal number the office did not intend to make public. Staff are adults, so a staff listing carries no minor-consent gate the way a student photo would; the school still controls exactly what is shown.

Translated family pages, said honestly

Not every family reads the school's default language first, and a message that only goes out in one language is not really reaching everyone. The shape of this lane is a consent-and-notice-gated translation of a staff-written message into a family's home language: a school employee writes the message, and the system is designed to translate it for the family that needs it — never the reverse, and never a general-purpose chat feature.

Two things are true about the design, and we say both plainly. First, it is built with exactly one translation path in mind, not a public or commercial translation service reached over the open internet. Second, and just as important: at this checkout, no live translation runs from this page yet. The engine that would actually perform a translation, the record of a parent's consent, and the record of a family's home language are not wired in here today. Rather than fake a translated page or quietly route a message through an outside service to look finished, the honest answer is that this capability is consent-gated by design and honest-off today.

Event sign-ups — consent first, capacity always honest

A staff member creates the event record — never a parent or a student, and never without the staff gate passing. Signing a family up for a seat is decided by one rule, checked in this order: consent, then capacity. A sign-up is confirmed ONLY with an explicit granted consent verdict — a missing answer or an unclear one is treated as a no, never assumed to be a yes. Only once consent clears does capacity matter: with room, the sign-up confirms; at the limit, it waitlists rather than overbooking or silently dropping the request; without room and without a waitlist, it is denied and says so.

That consent-and-capacity rule is a pure decision, built and tested on its own. What sits around it — the live store that records a confirmed seat, the confirmation notification a family receives, and event-day extras like a QR-token instant photo gallery, an on-site print sale, and moderated community-submitted candid photos — are configured per event and are early access: built as a staged rollout, not open on every event yet. Where those photo extras exist, sharing them is consent-walled the same way any other candid on the platform is.

Any photo on this site, said honestly

A school website naturally carries photos — a newsletter story, a staff headshot, an event gallery. Where a student appears, the same consent posture holds everywhere on this platform: a student's photo is shown only when a permission on file allows it, and facial recognition is off by default. There is no crowd face-scan running by default anywhere on this site.

A minor's photo is never made public without consent, never indexed by an outside search engine as a face lookup, and never sold. Where a family orders a print — from picture day or from an event gallery — that order routed to an outside print lab is fulfilled by that vetted partner, so not every step of a print order is kept fully in-house; we say so rather than promise otherwise.

What is built, what is early access, and what is honest-off

Built and wired today: the family newsletter (opt-in, adviser-composed, unsubscribe always honored) and the public staff directory (off the office's own staff roster).

Consent-gated by design, honest-off today: translated family pages. The lane is designed around consent + notice and one translation path; no engine is wired in at this checkout, so no live translation runs from this page.

Decision engine built, rest early access: event sign-ups. The consent-and-capacity rule that confirms, waitlists, or denies a seat is built and tested; the live registration store, confirmation notifications, and event-day extras (an instant photo gallery, an on-site print sale, moderated community candids) are a staged, early-access rollout.

Money is honest-off. Nothing on this page runs a live checkout. The newsletter, the staff directory, and the sign-up decision engine settle no money. Where money would eventually move — an event's on-site instant-sale till, a picture-day or event print order — those are early access and this page takes no payment.

What this is: Elementary School Website is a for-profit software product for elementary schools. It is not a school, not a district, and not a nonprofit. There is no charity or donation framing here, and none would be honest. There are no invented adoption numbers, testimonials, or named schools on this page. A conversation shows the current state honestly — what is built, what is consent-gated-but-not-live, and what is early access.

FAQ

Common questions

Is this the same as elementaryschool.site?

No, they are two distinct tiers of the same platform. elementaryschool.site is the “quick-start” whole-school family front door — online enrollment, the free student-records tier, permission slips, and a code-not-a-face picture-day store. elementaryschool.website is the fuller communications tier alongside it: a newsletter, a public staff directory, translated family pages, and event sign-ups. A school can run one or both.

Do families get added to the newsletter automatically from the roster?

No. A family subscribes itself with a double opt-in — an email address, then a confirm click. A subscriber row is never created from the class roster or the family directory. An unsubscribe is always honored on every issue.

Where does the staff directory get its information?

From the same staff roster the school's office already manages inside the platform — name and role, admin-managed. The public page shows a name, a role, and a school-chosen contact, and never more than the school decides to publish. Staff are adults, so no minor-consent gate applies to that listing.

Can a family actually get a translated page today?

Not yet. The design is a consent-and-notice-gated lane meant to translate a staff message into a family's home language using one translation path, not a public translation service reached over the open internet. But at this checkout no engine is wired in, so no live translation runs from this page. We say that plainly rather than fake a translated page.

How does an event sign-up decide who gets a seat?

By one rule, in order: consent first, then capacity. A sign-up confirms only with an explicit granted consent — a missing or unclear answer is always a no. With room, a consented sign-up confirms; at the limit, it waitlists rather than overbooking; without room or a waitlist, it is denied honestly.

Is the event sign-up fully live, including confirmations and photos?

The consent-and-capacity decision rule is built and tested. The live registration store, the confirmation a family receives, and event-day extras like an instant photo gallery, an on-site print sale, or moderated community candids are early access — a staged rollout, not open on every event yet.

Do you scan faces or run facial recognition on students?

Facial recognition is off by default. A student's photo is shown only when a permission on file allows it, a minor's photo is never made public without consent, never indexed by an outside search engine as a face lookup, and never sold.

Can I buy a print or check out on this page?

No, and we will not pretend otherwise. Nothing on this page runs a live checkout. The newsletter, the staff directory, and the sign-up decision engine settle no money; an event's on-site instant-sale till and print orders are early access. A picture-day or event print order that is routed to an outside print lab is fulfilled by that vetted partner, so not every step stays fully in-house.

Is elementaryschool.website a school or a nonprofit?

No. It is a for-profit software product — a vendor whose product is this platform for elementary schools. It is not a school, not a district, and not a nonprofit, and there is no charitable or donation framing here because none would be honest.

Bring a fuller website to your elementary school

One roster feeds a newsletter families opt into, a staff directory, a translated-page lane, and an event sign-up sheet. The newsletter and the directory are live and free to start reading about; translated pages are honest-off today, and event sign-ups are a built decision engine with the rest in early access. A conversation walks the whole thing honestly.