Core feature

Projects

Give a body of work its own scope, tasks, and deadline while keeping the notes where the real reasoning happens.

Start with the scope

A project gives a defined piece of work a home. Start with the outcome, the people involved, and the boundary that tells you what is in or out. You can then connect the notes that explain the work rather than rewriting them into a project board.

Project outline

Website launch
#project #launch

Outcome
Publish the new site with the onboarding flow ready.

Deadline
18th September

Next actions
- Confirm the final copy
- Review the release checklist

Keep project context connected

Projects are most useful when they point back to the notes where decisions, research, and updates live. Link the scope to a kickoff note, a decision log, or the task note that needs attention next.

This keeps the project view concise while preserving the reasoning behind its status.

Review progress without rebuilding it

Check the next tasks and their due dates.
Open the linked note when a decision needs context.
Update the scope when the outcome changes.
Leave a short note about what changed and why.

The goal is a clear working view, not another place where information can drift away from the work.

Projects are a Core feature. Notes, tasks, and tags remain the foundation; Projects add a shared scope when the work needs it.