Prototypes
Table of Contents
1. Summary
A prototype answers a question about layout or behaviour that a document argues badly. It is throwaway: static files, mock data, no framework and no backend. It exists so a design can be argued about with something concrete in front of you.
This page is the index. Each entry opens the prototype, and names the page that describes it.
2. The prototypes
| Prototype | What it argues | Open it |
|---|---|---|
| Trade entry | Trade entry belongs to the structure, not the trade. Manage the structure and its components, then price it and book it. | Booking screen |
3. Adding a prototype
- Put the static files under
doc/prototypes/<name>/. Plain HTML, CSS and JavaScript. No build step. - Deploy them with one call to
ores-deploy-web-appinsideores-deploy-web-apps, inprojects/ores.lisp/src/ores-build-site.el. - Describe the prototype on a knowledge page beside this one.
- Add a row to the table above.
4. See also
- Knowledge — the hub of all knowledge notes.
- Trade Structures and Deal Composition — the rules the trade entry prototype follows.