Access prototypes
Table of Contents
1. Summary
Roles, and the permissions each role bundles.
Three 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 |
|---|---|---|---|
| Access screens | A member's own roles and a “Can I…?” answer, the administrator giving and taking away roles with a reason, and a role catalogue whose permissions are a grid by area rather than a list of 890 codes. | prototype | Gemini review |
| See the story of a request | The role-request journey writes to six tables and each screen answers from one: whether one request's whole story belongs in one place, and which parts of it each reader may open. | prototype | none |
| Where requests live | The tenant's menu says Requests and an administrator hears my requests; a member never sees the word at all. Three ways to put the word where it means what it says, and who the door belongs to. | prototype | none |
3. Adding a prototype
Create doc/prototypes/access/<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/access/<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.
- Access journeys — the journeys these prototypes answer.