Getting started
Create a school
The four screens a new school walks, what each one asks for, and what does not happen until the four are finished.
A school can be created without a conversation: /signup, an email, and a name. This page walks the four screens, so a
reader knows what is being asked and what has not happened yet at each step.
Screen one: the address
/signup asks for two things, and one of them is a decision:
- where to reach you, which is the address the verification link goes to;
- the address your school will live at, which becomes the school's own host name.
The second is the one to think about. It is shown as a slug while it is being chosen and becomes a subdomain afterwards, so
a school that picks ashee-basic will sign in at ashee-basic. followed by the deployment's domain.
Nothing is created at this point: not a school, not a name reserved, and no card.
Screen two: the email
The link in the email carries a token and nothing else. Opening it proves the address is reachable, which is the whole of what it proves. The token travels in the query string rather than in storage, because a copy of the proof is a second chance to leak it.
Screen three: the school
/setup names the school and names its first administrator. The address chosen at sign-up is shown rather than asked for
again: a field asking for it a second time is a field where the two answers can differ.
Screen four: open it
The last screen says the school is ready and offers the link to it. The administrator signs in there, and setting up a school is the next page.