What
Be able to keep to-dos inside the editor — track tasks related to a flyer (or to the editor itself) without leaving the app.
Why
Right now there's nowhere to jot "still need a source for this stat", "ask X to proofread", "swap the logo before publishing". These notes live in the head or in some other app and get lost. A lightweight to-do surface keeps the working context next to the content it's about.
Open questions (to resolve before building)
- Scope: to-dos per concept (travel with the flyer, sync via Evolu like everything else) vs. a single global list for the editor? Likely per-concept, with maybe a global view that aggregates.
- Where it lives: a panel in the Sidebar? A tab next to History? An overlay?
- Model: new Evolu table (
conceptTodo: id, conceptId?, text, done, createdAt) so it syncs across devices via the mnemonic — consistent with concept/conceptSnapshot.
- Inline vs. structured: dedicated to-do items (checkbox rows) vs. just recognising
- [ ] checkboxes in the markdown body. Probably structured + separate from print content (to-dos must NOT render onto the printed flyer).
- Interplay with the AI bridge: could later expose to-dos to Claude (read/append) so it can pick up tasks — but that's a follow-up, not v1.
Notes
This is a surface/scoping issue — capturing the idea, not a committed design. Decide scope + storage model first.
What
Be able to keep to-dos inside the editor — track tasks related to a flyer (or to the editor itself) without leaving the app.
Why
Right now there's nowhere to jot "still need a source for this stat", "ask X to proofread", "swap the logo before publishing". These notes live in the head or in some other app and get lost. A lightweight to-do surface keeps the working context next to the content it's about.
Open questions (to resolve before building)
conceptTodo: id, conceptId?, text, done, createdAt) so it syncs across devices via the mnemonic — consistent withconcept/conceptSnapshot.- [ ]checkboxes in the markdown body. Probably structured + separate from print content (to-dos must NOT render onto the printed flyer).Notes
This is a surface/scoping issue — capturing the idea, not a committed design. Decide scope + storage model first.