Setup prototypes
Table of Contents
1. Summary
Standing up an installation: first run, a new tenant, a new party.
3 prototypes answer to this group. Each one is a static page under
doc/prototypes/, opens with no build and no session, and reads mock data
only. The table below opens each one and says what it argues. Where a
prototype carries a Gemini review, the last column opens it: a review is a
generated alternative kept beside the agreed design, never instead of it.
Prototypes is the top page and the only inventory.
2. The prototypes
| Prototype | What it argues | Open it | Review |
|---|---|---|---|
| First run | A new installation is welcomed, given its first account, and left either with a tenant built from a starting point or with the system tenant alone. | prototype | Gemini review |
| New tenant | A tenant is formed as a stepper that carries its own details and logo, with the super administrator's password started rather than asked for. | prototype | none |
| New party | A party is added as a journey on the shared journey page, and its members are the accounts that work in it. | prototype | none |
3. Adding a prototype
Create doc/prototypes/setup/<name>/ with an index.html, and a
prototype.css and prototype.js when it needs them. Open the page with
the links table every prototype carries, and leave its review row at
none. Add a row to the table above, with the design note beside the
prototype when there is one. Stop there: the site build finds every
prototype under this tree, so no build file names it.
A review goes at doc/prototypes/setup/<name>/review/, with an
index.html that lists its screens. The row names it, and the
prototype's review row points at it. Prototypes states the
whole method and the rules that hold for every group.
4. See also
- Prototypes — the top page: the groups, and the one way to add a prototype.
- Setup journeys — the journeys these prototypes answer.