The project dashboard
The screen a project opens on: a board of cards you arrange yourself, showing what is moving and what is waiting.
What it is for
A project accumulates faster than memory does. The dashboard exists to answer, in one look, the two questions you actually have when you sit down — what was I doing, and what is unfinished.
It is per project. Two projects can carry completely different boards, because a drafting novel and a campaign world want to know different things.
The cards
| Card | Shows |
|---|---|
| Recently updated | The records that changed most recently, of a type you choose |
| Recently visited | Where you have been, which is usually where you are going back to |
| List | A plain list of one record type — characters, chapters, locations |
| Plan summary | The state of a plan: what is done and what is not |
| Relations graph | A small view of the relation network |
| Suggestions | The work suggestions for this project |
| Publication | Reads and reach for a published story |
Arranging the board
Cards have a position and a size, and both are yours. Drag one to move it, drag its corner to resize it, and add or remove cards from the edit rail. The arrangement is stored with the project, so it is the same on every machine you sign in from.
A card bound to a record type asks you which — a list card can be your characters, or your chapters, or your entries, and you can have several of each pointed at different types.
When it is empty
A new project has no board. That is deliberate: a dashboard assembled before there is anything to show is a page of empty boxes. Add the first card the day you have a question the project could answer.
The dashboard is itself a module and can be turned off. If you do not use it, turning it off means a project opens on whatever you actually work in.