Publisher Software · the school as publisher · one multi-publication engine
One publishing house, every school publication — yearbook, newspaper, lit-mag, and more on one engine.
A school does not print one thing. It prints a yearbook, a newspaper, a literary magazine, a weekly newsletter, a graduation memory book, an event program, a family handbook, a staff or community directory. Publisher Software runs the whole house on ONE multi-publication engine: one roster, one student identity, one consent gate, and one print pipeline — every title set in the same editor and opened as a flip-book online edition anyone can read from a link. The editor, the publication ladder, the online editions, and the print pipeline are built and running today. The live distribution leg — pushing a newsletter to inboxes, an SMS or notification, a mailed printed edition — is honest early-access, named plainly. Nothing here is a fabricated stat or a roadmap sold as shipped.
This is the multi-publication product page — deep on the engine, the publication ladder, the flip-book online editions, and the consent-gated disclosure boundary. The news-only surface is the sibling schoolnews.software; the reporter’s desk is journalist.software; the yearbook publications surface is yearbook.press. Publisher Software is the house above them all. Money is honest-off: no pricing and no checkout on this page.
What Publisher Software is
At the center is a plain idea: a school is a publisher, and a publisher runs a house of publications rather than a single title. Publisher Software is the engine for that house. The same editor that lays a yearbook spread lays a newspaper front page, a literary-magazine poem, a weekly newsletter, an event program, a family handbook, and a staff or community directory. The office does not learn a new tool per publication; it runs them all on one engine.
Every one of those runs on the same student record: one imported roster, one student identity, one consent gate, one print pipeline, one flip-book online-edition read surface. A photo cleared for the newspaper is the same consented asset the yearbook respects; a student who leaves the roster leaves every publication at once. The breadth is the point — the rules a school sets once are honored across the whole house, automatically, instead of fragmented across a separate tool and a separate invoice per title.
Honestly, where the build is: the multi-publication ladder and its fail-closed type gate, the multi-publication editor, the flip-book online editions, the print pipeline, and the consent-gated disclosure boundary are built and running today. The one honest-off surface is live distribution — the outbound send that pushes a piece to inboxes or the mail — and this page names it plainly as early-access rather than claiming a live send.
The engine: what is built and what is in early access
The house has six surfaces. Five are shipped and running — the multi-publication ladder, the one editor, the flip-book online editions, the print pipeline, and the consent-gated disclosure boundary. The sixth — live distribution — is honest early-access. Each is marked plainly.
The multi-publication ladder
The engine reasons over a shipped ladder of publication types — yearbook, newspaper, magazine, program, handbook, litmag, and directory — and no type is privileged over another. A title is producible only when the print vendor has DECLARED it can make that type: the printer capability gate is default-deny on type and fail-closed, so an undeclared type is never made, never silently substituted. A newsletter is set as a recurring publication on the same engine, and a memory book is a yearbook-family book on the same engine — compositions the one engine sets. Shipped
One editor for every title
The multi-publication editor sets a yearbook page, a newspaper front page, a lit-mag spread, a newsletter, a program, and a directory in one place, on one roster and one identity. The adviser and the staff do not switch tools between publications; the same page-building surface serves the whole house, so a school running five publications runs one editor, not five. Shipped
Flip-book online editions
Any published title opens on any phone from a link, no app to install, as a flip-book online edition on the same read-side surface the yearbook online edition uses. The online edition is the always-available read path — a stable URL a family can open where they are — and it is distinct from the outbound push, which is the early-access distribution leg named below. Shipped
The print pipeline, fail-closed
Every title in the house sets to a print-ready page on the same print pipeline and VDP flat-paper rail. Print preflight blocks by default: a missing font fails the job rather than silently substituting a different one, so what prints is what the staff laid out. One production path produces the yearbook, the newspaper, the lit-mag, and the program alike. Shipped
Consent-gated disclosure
Any publication that discloses student-coupled information — a name, a photo, an award tied to a student — routes through the consent substrate at the emit boundary. The check happens at the moment the detail would be emitted into a published piece, not left to a reviewer to remember. A student-coupled detail without consent on file is not emitted, and that transport is never sold and never made public. The public voice of the house is loud, but it is gated. Shipped
Live distribution / send
The outbound send — pushing a newsletter to family inboxes, firing an SMS or notification blast, or dropping a printed edition into the mail — is honest early-access. Composition, print-ready generation, and the flip-book online edition are built; the live send is the early-access step. This page does not claim a live send and never renders a fabricated delivery. What is available today is writing the title, setting it print-ready, and posting the online edition anyone can open from a link. Early access (live distribution)
The publication ladder: one house, many titles
Publisher Software does not privilege the yearbook. The engine treats every publication type the same way — each is a real product a print vendor must declare it can make — and sets them all on one roster, one editor, one print pipeline. Here is the ladder, in plain terms.
Yearbook
The book of the year — portraits, spreads, and the desktop-class layout the platform is known for. A declared publication type on the ladder, and the reference title the print pipeline and flip-book edition are shared from.
Newspaper
A student newspaper and its online news site — one staff, one reporting cycle, two surfaces. A declared type on the ladder. The news-only front door is the sibling schoolnews.software; the reporter’s desk is journalist.software.
Literary magazine
The litmag — student poetry, prose, and art set as a magazine. A declared type on the ladder, produced on the same engine as the yearbook and the newspaper rather than in a separate design tool.
Newsletter
A recurring newsletter is set as a publication on the same engine — the office writes it once and it sets print-ready and posts as a flip-book online edition. Composition and the online edition are built; the outbound push is the early-access distribution leg.
Memory book
A graduation memory book is a yearbook-family book the same engine sets — a keepsake volume for a class or a program. It is a composition on the engine, described plainly, not a separately branded product.
Program, handbook, directory
An event program, a family or staff handbook, and a staff, student, or community directory are each declared types on the ladder. The same editor and the same print pipeline set them, gated on the print vendor declaring it can make that type — default-deny, fail-closed.
Flip-book online editions: the read surface for the whole house
Every title the house publishes has a read side, and it is the same read side for all of them: a flip-book online edition that opens on any phone from a link, with no app to install. A family reads the newsletter, the newspaper, or the yearbook where they are, on the device they have, at a stable URL. The online edition is the always-available read path — it is posted and readable whether or not the early-access outbound send has fired.
This matters for how the house behaves. The read path is distinct from the push: posting a flip-book edition a family can open is not the same as blasting it to their inbox. Publisher Software ships the read path today and names the push as early-access. A published title is real and readable at its link; the outbound distribution that would deliver it to a mailbox or an inbox is the early-access step, said plainly rather than implied.
One print pipeline, fail-closed by default
A publishing house needs its printed output to be trustworthy, so every title sets to a print-ready page on the same print pipeline and VDP flat-paper rail — the yearbook, the newspaper, the lit-mag, the program, and the directory alike. There is one production path, not one per publication, which is why the house is one engine and not a drawer of disconnected tools.
The print preflight blocks by default. A missing font fails the job rather than silently substituting a different typeface; an out-of-gamut asset or a bad bleed is caught before it prints, not after. What comes off the press is what the staff laid out. This is a deliberate fail-closed posture: the pipeline would rather stop and tell you than quietly change your publication.
To be plain about scope: the print-ready generation is built and runs today. The outbound send — where a printed edition goes into the mail — is the early-access distribution leg, named honestly. The line between generation and delivery is drawn on purpose: the page never presents the mailed send as available today.
Consent-gated disclosure: a loud public voice, gated at emit
A publishing house speaks to families and the community — that is the point. But a school’s publications brush against student-coupled information: a name in an honor roll, a photo in a spotlight, an award tied to a person. Publisher Software treats that boundary as the same consent boundary the rest of the platform enforces, not a lighter one because a publication is public.
The disclosure check happens at the emit boundary. A draft stored in the editor is not a disclosure — it is internal content. The disclosure event is the moment a student-coupled detail would be emitted into a published title or an outbound send, and that emission routes through the consent substrate: the consent record is checked at the emit call, not in a reviewer’s memory and not in the database. A student-coupled detail without consent on file is not emitted into the public piece.
The audience is roster-scoped and tenant-isolated, and the data is handled honestly. A publication is scoped to one school’s imported roster; tenant isolation at the data layer means a title for one school is never resolvable against another school’s families. A student’s coupled record is never sold and never made public beyond what consent allows. This is not a “we hold no data” claim — a publication that names a student IS working with student data. The honest claim is that the disclosure is consent-gated at emit, private, never sold, and never carried into anything shared.
Live distribution: named plainly as early-access
The one honest-off surface on this page is the outbound send. Publisher Software builds the write side and the read side of the whole house — composing a title, setting it print-ready, and posting the flip-book online edition. What is early-access is the delivery leg: pushing a newsletter to family inboxes, firing an SMS or notification blast, or dropping a printed edition into the mail. The page does not claim a live send, and it never renders a fabricated delivery.
We draw the line on purpose. Composition and print-ready generation and the online edition are built. The live send is the early-access step, and we say so plainly rather than presenting a blast as available today. When the distribution backend lands and is real, it will be labelled real — not before.
Money is honest-off here as well. There is no pricing on this page and no checkout — the product does not process a payment on this surface, and there is no purchase to make here. If a paid distribution service is ever offered, it will be a separate, consent-first decision, said plainly. The honest next step is a conversation, not a checkout.
The house, above any one title
There is more than one way to talk about school publishing, and Publisher Software keeps the surfaces distinct rather than blurring them into one vague claim. Each sibling is a real, separate piece; this page is the engine above them.
Publisher Software (this page)
The multi-publication engine itself: the whole house of publications on one roster, one editor, one consent gate, one print pipeline, one flip-book read surface. It is the ladder and the engine, not a single masthead.
schoolnews.software
The news-only publication surface — one publication type, the school news site. Distinct from the house: it is a single title, run on the same engine, not the whole ladder.
journalist.software
The reporter’s desk — the author’s workflow, the pitch-to-published cycle for the person writing. Distinct from the house: it is the writer’s surface, not the engine that runs every publication.
yearbook.press
The yearbook publications surface — the book of the year on the shared publications engine. Distinct from the house: it is one title on the ladder, the reference the print pipeline and flip-book edition are shared from.
Common questions
What does Publisher Software actually run?
A whole house of school publications on one multi-publication engine: a yearbook, a newspaper, a literary magazine, a newsletter, a memory book, an event program, a family handbook, and a directory. They share one imported roster, one student identity, one consent gate, one editor, one print pipeline, and one flip-book online-edition read surface. It is the engine and the ladder, not a single title.
How is this different from schoolnews.software or journalist.software?
schoolnews.software is the news-only surface — one publication type. journalist.software is the reporter’s desk — the author’s writing workflow. Publisher Software is the house above them: the multi-publication engine that runs the whole ladder of publication types on one record. yearbook.press is the yearbook title on that same engine. We keep them distinct rather than blurring them together.
Are all of these publication types really built?
The engine reasons over a shipped ladder of declared publication types — yearbook, newspaper, magazine, program, handbook, litmag, and directory — with a fail-closed, default-deny-on-type printer capability gate: a title is producible only when the print vendor has declared it can make that type. A newsletter is set as a recurring publication on the same engine, and a memory book is a yearbook-family book on the same engine. The multi-publication editor, the flip-book online editions, and the print pipeline are built and running today.
Can Publisher Software send a newsletter to families today?
It can compose the newsletter, clear any student-coupled disclosure through the consent gate at the emit boundary, set it to a print-ready page on the print pipeline, and post a flip-book online edition families can open from a link. The live distribution — pushing the newsletter to inboxes, an SMS or notification blast, or a mailed printed edition — is honest early-access. We name that plainly. The page does not claim a live send.
What is the flip-book online edition, and is it available now?
It is the read-side surface: a published title opens on any phone from a link, with no app to install, on the same read surface the yearbook online edition uses. It is built and available today. It is distinct from the outbound push — a family can open the online edition at its URL whether or not the early-access distribution leg has fired.
What stops a publication from exposing a student's information?
The consent gate at the emit boundary. Any publication that would disclose student-coupled information — a name, a photo, an award tied to a student — routes through the consent substrate at the moment the detail would be emitted. A student-coupled detail without consent on file is not emitted into the public piece. The check is at emit, not in a reviewer’s memory and not in the database, and the data is never sold and never made public beyond what consent allows.
Do I need a different tool for each publication?
No — that is the point of the house. One multi-publication editor sets every title, on one roster and one identity, and one print pipeline produces them all. The adviser and the staff do not switch tools between the yearbook, the newspaper, the lit-mag, and the newsletter. A school running five publications runs one engine, not five.
How much does it cost?
There is no pricing on this page. Money is honest-off — no checkout and no card charged on this surface. The specific numbers are set for your program and shared in a conversation. The honest next step is to book a conversation and talk through what your publications office needs, not to check out.
Does Publisher Software make any charitable-status claim?
No. It is a for-profit publishing engine and makes no charitable-status or tax claim, and it is not legal or financial advice. It runs the school’s house of publications honestly; the school and its advisers remain the authority on their own program.
Related surfaces
Publisher Software is the multi-publication engine. These adjacent destinations cover the individual titles that run on it and the wider module catalog.
schoolnews.software
The news-only publication surface — the school news site as a single publication type. One title on the same engine; distinct from the whole-house ladder this page runs.
journalist.software
The reporter’s desk — the author’s pitch-to-published workflow for the person writing. The writer’s surface, distinct from the engine that runs every publication.
yearbook.press
The yearbook publications surface — the book of the year on the shared publications engine and the reference title the print pipeline and flip-book edition are shared from.
schoolsoftware.app
The plain-language K–12 module catalog front door, where an administrator scans every built module with honest per-module status. Multi-publication publishing is one line item there; this page is its full home.
What is built and what is honest-off
The multi-publication ladder — a shipped registry of declared publication types (yearbook, newspaper, magazine, program, handbook, litmag, directory) gated by a fail-closed, default-deny-on-type printer capability gate — is built and running today. The multi-publication editor that sets every title on one roster, the flip-book online editions that open on any phone from a link, and the print pipeline with block-by-default preflight are built and running today. The consent-gated disclosure boundary — any student-coupled detail checked through the consent substrate at the emit boundary, never sold and never made public — is built and running today. A newsletter is set as a recurring publication on the same engine, and a memory book is a yearbook-family book on the same engine. The one honest-off surface is live distribution: the outbound send (a newsletter to inboxes, an SMS or notification, a mailed printed edition) is honest early-access — composition, print-ready generation, and the online edition are built, and the live send is named as the early-access step plainly. There are no invented stats, testimonials, or user counts on this page, and no competitor brand names. Money is honest-off: no pricing and no checkout. The honest next step is to book a conversation.