Skip to main content
Version: Next (nightly)

Projects

The Projects module is for the work you do, not just the stuff you keep. A project groups the things a piece of work involves and tracks it from idea to done.

Tracking work​

  • A project has a status you move it through, dates, and the fields you care about.
  • A project can point at the parts, machines, or other items it depends on, because everything shares the same data.

What a design needs​

A design's materials and hooks pickers search your whole stash. Type a name and the picker finds it across every table, showing what is free, and when the stash is bigger than one page the list says so at the top. A hook a design already needs is listed whatever else the stash holds.

Tasks​

A project breaks into tasks: a title, an optional description, a status, a priority, a due date, and an energy level for sorting work by what you have in you.

  • Add one inline on the project's own page, tick it done from the row, and open it for the rest.
  • A task is a full record of its own, so it shows up everywhere records do: on the dashboard's overdue row (its own due date counts, and up to three tick off right there), in the Up next list, on a calendar or gantt view, with its own QR label if you want one on the bench.

Waiting on something else​

  • Mark a task as waiting on another task, or on any record such as an order that has to arrive first. The task reads as blocked, with a count of what it is waiting for, until that is satisfied.
  • When the last blocker clears (the order arrives, the other task completes), the workspace emits a task-unblocked event, which is wired to a notification out of the box, so the work tells you when it can start instead of you polling it.
  • Cobb can set and remove dependencies from a sentence: "this one is waiting on the filament order".
How far a dependency reaches

The linking is the point: a task's dependency can reference any record in the workspace. A task waits on another task, on a part being in stock, or on a print finishing, and the platform flips the dependency when it happens (stock arriving satisfies the tasks waiting on that part, out of the box). Your project board unblocks itself.

The pattern or manual behind it​

A project can hold the file the work follows: a pattern, a manual, a spec sheet.

  • Attach a pattern PDF and the finished-object photo is pulled out for you, reading the images the PDF embeds and picking the real photo over the diagrams, so you skip a separate upload.
  • other images in the pattern appears in the pattern & photos panel when the PDF holds more than one image. Open it to see everything that was extracted and tap one to use it instead.
  • A pattern that is all charts and diagrams gets no photo attached automatically. Open the strip and choose by hand.
  • A project that already had a pattern but no photo picks one up the next time you open it.

Seeing it your way​

  • A kanban grouped by status is the natural view for work in flight.
  • A calendar is better for anything with dates.

Same projects, different lens.