Books and portfolios prototypes
Table of Contents
1. Summary
The book structure: portfolios that hold books, the classification a book carries, and the rights that decide who may see it.
1 prototype answers 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 |
|---|---|---|---|
| Shape the book structure | A book is a leaf under a portfolio, so shaping the structure means showing what a book reads from its portfolio, keeping the tenant’s own books apart from the shared taxonomy they name, refusing a close the book cannot make, and a second person's approval for every gated act: the request waits, the checker decides, and a decline leaves the book alone. | prototype | none |
3. Adding a prototype
Create doc/prototypes/books/<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/books/<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.
- Books and portfolios journeys — the journeys these prototypes answer.