middleschool.today · For middle-school families · Grades 6-8
A middle-school day is not one classroom: it is class-level announcements from five or six different teachers, a rotating day pattern, a club or a first team that may or may not meet this afternoon, and the occasional message from the school. middleschool.today gathers today’s pieces onto one page so a family checks ONE place, not five separate systems, for what today actually holds.
This gathered view is in active development. No school is running it live yet, and money is honest-off -- there is no live charge on this page. The picture-day store and texted alerts are early access.
Why a today page, not another whole program
Three things about the middle-grades day make a same-day glance the right shape -- not a nice-to-have layered on top of the program, the hub, the publications editor, and the roster technology the platform already runs.
Many middle schools run an A day and a B day, or a block/modular period length on top of the advisory anchor -- so 'what does today look like' is a genuinely different question from 'what is the program.' The schedule solver already treats that rotation as a structural fact when it builds the whole timetable; a family does not need the whole scheduling engine to benefit from that, just a page that reflects it.
A class-level announcement -- a reminder, a heads-up, a note about something due Friday -- is timely by nature. It belongs on a page a family reopens daily, not buried in the same place as the whole-year program, the publications editor, or the roster-sync technology underneath all of it.
Whether a club or a first team meets is a quarter-by-quarter question middleschool.software and middleschool.technology already answer structurally. Whether it meets TODAY is a same-day glance a family actually wants each morning, distinct from the program page and the roster-sync story underneath it.
What the today page gathers
Each pillar below already exists on the platform, or is cross-linked to the surface that owns it; this page describes how a family reads it from the TODAY angle rather than describing it as a new engine.
A teacher posts an announcement to their own section, and enrolled students and their guardians see it in a reverse-chronological stream on the class page. An announcement is either PUBLISHED or a DRAFT -- a draft is visible ONLY to the teacher who wrote it, never to a student, until it is actually published. A viewer who is not enrolled in that section gets NOTHING, not a partial or redacted version. The announcement body is an opaque reference to the real text -- never reproduced or invented here -- and no student name, email, or id crosses this engine's boundary, only opaque section and author references.
Built · fail-closed to enrollment · no PII
An A day, a B day, a block or modular period length, sitting alongside the advisory or team anchor -- the deterministic whole-timetable solver treats that day-pattern rotation as a first-class structural constraint when it places the entire schedule, the same engine middleschool.software and middleschool.center already describe. This page does not invent a second, live per-calendar-date lookup: the honest claim is narrower and real -- the placed schedule already reflects the day pattern, and a section that cannot be placed is left unplaced with a reason, never forced into a clash.
Built · structural fact, not a new live calendar
Whether a club or a first team meets is a consent-and-capacity decision the platform already makes, fail-closed: consent is checked before capacity, and a request that cannot be confirmed is WAITLISTED, never silently dropped. That full safety-rails story belongs to middleschool.software, cross-linked below; this page adds nothing new to the engine, it only surfaces the same-day answer a family actually wants -- is there a meeting today.
Reads middleschool.software's engine · not re-described here
A message about today rides the same consent-gated family_comms lane the platform uses everywhere -- the SAME engine middleschool.center already reads from the staff-sending side; this page reads it from the family-RECEIVING side. In-app delivery is always available; email or text go out only where a family has opted in. A routine note defers during a family's quiet hours; a genuine alert overrides them, because that is the life-safety lane, not the daily-note lane. Deliveries are de-duplicated, and an event that fails validation sends nothing at all.
Built · consent-gated · fail-closed
A middle school's front office can already run its own recurring bulletin as a real publication -- dated editions, a print-ready page for the office board, and an online edition anyone can open from a link. That is bulletin.software's whole job, not this page's: middleschool.today does not rebuild the archive or the print pipeline, it is simply the fast link out to it, cross-linked below rather than duplicated here.
Built at bulletin.software · cross-linked, not duplicated
Middle School Today is a family-facing daily glance: the page a parent or a middle schooler reopens every day to see what TODAY holds -- class-level announcements, the day’s schedule pattern, whether a club or practice meets, and any family message that arrived. It is not the whole middle-grades program, not a staff caseload hub, not a publications editor, not the roster-sync technology underneath, and not a generic bulletin-publishing product -- those are five separate, already-bespoke surfaces, and this page cross-links each rather than re-describing it.
Concretely: elementaryschool.today is a SAME-DAY ONBOARDING speedrun for the stage below -- a roster import that turns into a working directory and real class pages within hours -- a one-time setup page, not a daily habit. middleschool.software is the year-round program front door -- electives, activities safety rails, standards report cards, counselor and MTSS supports, the move up to high school. middleschool.center is the STAFF-facing hub an advisory teacher or counselor opens for their group. middleschool.press is the publications editor a student staff runs the yearbook and newspaper in. middleschool.technology is the roster-sync technology underneath all of it. bulletin.software is the generic, cross-fleet home for the recurring bulletin as its own publication. middleschool.today is none of those: it is the one page a family actually reopens each day, gathering the same-day slices of each without rebuilding any of them.
Before the day starts, a parent opens middleschool.today for their student and sees, in place: any class-level announcement a teacher published overnight (a draft stays invisible until the teacher actually publishes it); today’s day pattern -- an A day or a B day, the block or modular periods, the advisory anchor -- already reflected in the placed schedule; a same-day answer on whether today’s club or practice meets, fail-closed to consent and capacity; and any family message that came in, on the channel the family actually opted into. It is the SAME records every teacher, the front office, and the roster technology already work in; this page’s only job is gathering the same-day slice of each, in one place, instead of five.
Nothing here replaces a teacher’s own class page, the front office’s own bulletin at bulletin.software, or the family’s own preferred channel -- it reads all three, for today, in fail-closed, consent-gated view.
Gathering today’s announcements, schedule, and messages onto one page does not lower the stakes on who can see it. A class-level announcement stays fail-closed to enrollment -- a viewer who is not enrolled in a section sees nothing, and a draft is invisible to anyone but the teacher who wrote it. Family messages ride a consent-gated channel a family can withdraw at any time.
Facial recognition is off by default. Family communication rides a consent-gated channel a family can withdraw at any time, and who can see a student’s roster entry and photos follows the access permissions a school sets. A picture-day order routed to an outside print lab is fulfilled by that vetted partner, so not every step is kept fully in-house -- and we never sell your data. The honest, keepable posture is the narrower one: consent-gated, off by default, and under the school’s own access controls.
What is built and what is honest-off — plainly
Built and wired today, on the same platform this page reads: the class-level announcement stream, fail-closed to enrollment with drafts visible only to their author; the day-pattern (A/B, block/modular) structural constraint inside the whole-timetable solver; consent-gated, quiet-hours-aware family messaging with de-duplicated delivery; and the consent-and-capacity activities engine middleschool.software fully describes. bulletin.software is a separate, already-shipped publication this page cross-links rather than rebuilds.
Honest-off: the single, gathered TODAY view itself -- the one page a family opens live, every morning -- is IN ACTIVE DEVELOPMENT; no school is running it live yet. Money is honest-off across this page: no live billing, no subscription, no live payment; the picture-day store and texted alerts are EARLY ACCESS, matching the standing platform posture. Middle School Today is FOR-PROFIT software for middle schools; it is not itself a school, a district, or a nonprofit. Nothing here is legal or medical advice.
FAQ
elementaryschool.today is a same-day ONBOARDING speedrun -- a roster import that turns into a working directory and real class pages within hours. It is a one-time setup page. middleschool.today is the opposite shape: a page a family reopens EVERY day, long after setup is done, to see what today holds -- class-level announcements, the day's schedule pattern, club/practice status, and family messages.
Each is a distinct surface on the same platform. middleschool.software is the year-round program front door (electives, activities safety rails, standards report cards, counselor/MTSS, the move up to high school). middleschool.center is the STAFF-facing hub an advisory teacher or counselor opens for their group. middleschool.press is the publications editor a student staff runs the yearbook and newspaper in. middleschool.technology is the roster-sync technology underneath all of it. middleschool.today is none of those -- it is the family-facing daily glance, gathering same-day slices of each without rebuilding any of them.
No. bulletin.software is the generic, cross-fleet product home for the recurring school bulletin AS A PUBLICATION -- dated editions, a print-ready page, an online edition, a running archive -- and it says nothing about middle school specifically. middleschool.today does not rebuild that publication engine or claim its archive/edition mechanics; it cross-links bulletin.software as the front office's own bulletin and instead gathers a different, middle-grades-specific set of same-day pieces: class-level announcements, the day pattern, club/practice status, and family messages.
No, either way. An unpublished announcement is a DRAFT visible only to the teacher who wrote it -- a student never sees it. A viewer who is not enrolled in a section gets nothing for that section's announcements, not a partial or redacted version; enrollment is checked before anything is shown.
Not as a separate live lookup on this page. The day-pattern rotation (A/B, block/modular) is a structural constraint the whole-timetable solver already honors when it places the schedule, so the placed schedule reflects the pattern. We are precise about the difference: the structural fact is built; a standalone live per-date calendar feature is not a separate claim we make here.
No. That engine -- owned and fully described by middleschool.software -- checks consent before capacity, and a request that cannot be confirmed once a group is full is WAITLISTED, never silently dropped and never pushed past the cap. This page only reads the same-day answer; it does not change how that engine decides.
A message rides the same family_comms consent lane used across the platform -- the same engine middleschool.center reads from the staff-sending side. In-app delivery is always available, while email and text are sent only where a family has opted in. A routine update defers during a family's quiet hours; a genuine alert overrides quiet hours because that is the life-safety lane. Deliveries are de-duplicated, and an event that fails validation produces no send at all.
The gathered today-view over records, announcements, and messages settles no money; money is honest-off across the platform today, including the picture-day store, which is early access alongside texted alerts. Middle School Today is in active development and no school is running the gathered view live yet. The honest next step is a conversation that shows the current state plainly -- what is built, what is honest-off, and what is early access. Email [email protected].
Today's class-level announcements, the day's schedule pattern, club and practice status, and family messages -- gathered onto one page a family actually reopens each day, instead of five separate systems. The gathered view is in active development, and a conversation walks through what is built, what is honest-off, and what is early access, honestly. Money is honest-off; there is no live charge on this page.