School photography, one gallery address per district

k12.gallery

One gallery domain for a whole district -- elementary, middle and high school under a single family-facing address, instead of a separate ordering link per building or grade band.

No district routes family gallery links through this host today. The underlying proofing and ordering engine is built and already serves families under the .photos family of sites; k12.gallery is not wired as an entry point to it today.

What k12.gallery is

A district today hands families a different link per school -- one for the elementary building's photo day, a separate one for the middle school, a third for the high school senior studio. Each link points at the same underlying proofing/ordering engine but wears a different, unmemorable address. k12.gallery collapses that into ONE domain: k12.gallery/<district-slug> routes to the right building automatically once a family signs in, so the district communicates a single URL in every newsletter, ID card and enrollment packet, for every grade band, every year.

It is a naming and routing layer over capability that already exists in the estate -- consent-gated proofing, family sign-in, and print/digital ordering all run today under the .photos family of sites. k12.gallery does not invent a new photography workflow; it gives a district one gallery front door instead of several.

Who it's for

District communications office
One URL to print on every family-facing document for the whole year, instead of re-issuing a new link each time a different school's photo day happens.
Building-level photo coordinators
A shared address families already recognize, rather than training each building's front office to hand out its own unique proofing link.
Families with children in more than one building
One sign-in surfaces every child's gallery, elementary through high school, rather than three separate bookmarked links.
A studio serving a whole district under contract
A single branded domain to hand the district instead of building one-off subdomains per contract renewal.

How it works

  1. 1

    District slug is registered

    The district's existing gallery/ordering configuration is mapped to a slug under k12.gallery -- no new consent flow, no new data store; it points at the same records the .photos-family gallery already serves from.

  2. 2

    Families sign in once

    A parent or guardian authenticates the same way they do today (school-issued credential or verified email match), and every child enrolled under that guardian in the district resolves to their gallery -- no separate link per building.

  3. 3

    Proofing and ordering run on the existing engine

    Photo selection, consent-gated viewing, and print/digital ordering use the same underlying flow already live for the .photos family -- k12.gallery changes the address families reach it at, not the flow itself.

  4. 4

    The district keeps one address across years

    Because the routing lives at the district-slug level, a new photo day, a new building, or a new grade band does not require issuing a new link -- k12.gallery/<district-slug> stays constant.

What actually changes at the resolver level

The three gallery views on the right are not new -- they are the same consent-gated proofing engine already serving the .photos family today. The only new component is the box in the middle: a district-slug resolver that reads a guardian's enrollment records and fans one sign-in out to every building that guardian has a child in. No new data store, no new consent record, no new photography workflow -- one routing hop added in front of capability that already exists.

Today, the same three boxes on the right exist, but a guardian holds a separate bookmarked link to each one and re-authenticates at each building's own address. The middle box is the entirety of what k12.gallery adds.

Today's per-building links, side by side with k12.gallery

This compares a district's OWN current workflow -- separate links issued building by building -- against routing the same underlying engine through one district-wide address. No other vendor or platform is named or implied on either side of this table.

QuestionToday, per-building linksWith k12.gallery
How many links a family holdsOne per building the family has a child in -- three separate bookmarks for a K-12 household.One: k12.gallery/<district-slug>, resolving to every enrolled child automatically.
What happens when a child moves from elementary to middle schoolThe family's old proofing link stops resolving to that child's gallery; the district or building must issue a new one.Nothing changes for the family -- the same address keeps resolving to wherever that child is enrolled.
What the district prints in a newsletter or enrollment packetA different link per building, reissued whenever a building's photo vendor or ordering page changes.One address, stable across grade bands and photo days, printed once per year.
Who trains the front office to hand out the right linkEach building's staff separately, since each building's link and instructions differ.The district communications office once, since every building resolves under the same slug.
What happens to consent and proofing data underneathLives in the same estate-wide proofing/ordering engine as it does with k12.gallery -- this row does not change.Identical -- k12.gallery is a routing layer over the same engine, not a new place minors' data lives.

Questions districts ask

Is this a new photo system districts have to migrate to?

No. k12.gallery is a routing layer over the estate's existing proofing/ordering engine -- the same one the .photos family serves families from today. A district does not migrate data; a slug is registered against records that already exist.

Can our families use k12.gallery today?

No, not today. Nothing routes through this host today; the domain is owned and the brand is written, but no district slug is live. This page will say so plainly, and this sentence changes the day it does, from the same launch latch, not a copy edit made separately.

Does k12.gallery expose student photos to the public?

No. Every gallery behind this domain is consent-gated exactly as it is under the .photos family today -- sign-in required, no public index of student images. Minors' data is never made public through this surface.

Is a separate platform account required to use k12.gallery?

No. k12.gallery is an independent product with its own sign-in -- it is not required, and k12.gallery does not sit under any other brand.

What happens to a family's existing per-building bookmarks if a district adopts k12.gallery?

They keep working -- registering a district slug does not remove or redirect a building's existing proofing link. The district-wide address is an addition families can migrate to at their own pace, not a forced cutover of links already handed out.

What does k12.gallery cost?

No price is charged through this surface today. See the pricing section below for why, rather than a bare 'not available' label.

What this costs a district

No price renders on this page and no checkout link is live. That is not a placeholder waiting to be filled in -- it reflects that no billing decision has been made for k12.gallery specifically. The underlying proofing/ordering engine already handles payment for the .photos family of sites; whether k12.gallery bills a district separately, folds into an existing studio contract, or ships as a no-additional-charge address change is a decision this page does not get ahead of.

Two things stay true regardless of how that decision lands: money handling on this surface is honest-off until it is explicitly turned on, matching every unwired product across the estate, and no figure, discount, or "free" claim appears here until it is real and charged.

What's true today

SurfaceStatus
District-slug routing through this hostNot switched on. No district resolves at this host yet.
Proofing, sign-in and ordering engineBuilt and live today, reached through the .photos family of sites -- k12.gallery is not wired today as a second entry point to it.
Payment / checkout on this pageHonest-off. No live checkout link renders from this surface, because no billing decision for this host has been made -- see the pricing section above.
Public gallery indexDoes not exist and will not -- every gallery view stays consent-gated and sign-in-required, matching the estate's minors'-data rule.

Family-similar only within the K-12 grade-band family; k12.gallery is its own brand, not a re-skin of any sibling above. A district that wants a single grade band instead of the whole K-12 span registers under one of the single-grade-band siblings above, not this host.

Works with Homeroom -- an optional integration for districts that also run it. Not required to use k12.gallery.