Prototypes ZibaldoneP24 · Zibaldone plan
Zibaldone plan
?
How Zibaldone is built
  1. The model is Zibaldone’s: a task and its rules, where a change to the status sets the time it was done and every change adds a line to the task’s log.
  2. Board, list, month and timeline are four layouts of the same tasks. Zibaldone’s view engine picks, groups and orders them for the board and the list, and its month and timeline helpers place them on dates.
  3. Quick add reads a line the way people write it, in English or Danish: a date, a deadline, !2 for a priority, # for a list, @ for a label and a repeat such as every monday. Each piece it reads is shown before you press Enter.
  4. A card dragged to another column takes that status and a rank between its new neighbors, so the order holds on every screen. A repeating task that is done adds the next one.
  5. Each task is a Y.Map of its fields, so two people who change different fields of one task keep both changes. The plan syncs encrypted over P14’s relay, with the key in the link after the #. When a member is removed from the workspace, the plan moves to a new key: a signed record in the old document gives this device the new workspace key in a sealed envelope (zib/move.mjs), and the page opens on it where it was. The removed person’s page says who removed them.