Creating a Project
Projects are intentionally minimalist - a name and an optional description. Creating one takes a few seconds.
Naming the Project
Give the project a short, clear name that describes the context it's grouping:
| Works well | Doesn't work as well |
|---|---|
| "Work" | "Stuff" |
| "Home renovation" | "Home" (if you already have "Home maintenance") |
| "Side hustle - app launch" | "Project 3" |
The name is how you'll identify the project in filters and on task cards, so make it something you'll recognize at a glance.
Adding a Description
Optional. A sentence or two if the project needs more context than the name alone provides. Most projects don't need descriptions - the name is enough.
Descriptions are encrypted at rest alongside the project name.
Where to Create One
Project creation is tucked into Settings under a project management screen. It's not a high-traffic area - you create projects once and then mostly ignore the management screen after that.
From the management screen you can:
- Create a new project.
- Rename an existing project.
- Delete a project.
- See task counts for each project at a glance.
Saving and Editing
Saving is instant. The project appears in the project filter dropdown on the Lifegrid the moment you confirm.
After creation, you can freely edit the name and description. Changes don't affect the tasks already inside the project.
Deleting a Project
Deleting a project gives you a choice about what to do with its tasks:
- Move tasks to Personal (the default) - the project vanishes but the tasks stay. This is the safe option.
- Delete everything - the project and all its tasks are removed. Use with care.
There's a confirmation modal either way since both options are irreversible.
Deleting a project with history
A project might have dozens of completed tasks in its history. Deleting the project with "delete everything" also deletes those completed records - your silver balance is unaffected (it recomputes from the event ledger), but the individual task records are gone. If you want to preserve history, move tasks to Personal instead.
What Projects Don't Have
To ground expectations, projects deliberately skip:
- Colors or icons - name-only differentiation.
- Priority levels - tasks have their own priority if needed; project-level priority would add complexity without real benefit.
- Deadlines - projects are buckets, not goals. If you want a deadline, you want a goal.
- Nesting - flat only. "Sub-projects" would start to compete with sub-goals, and one nesting hierarchy is enough.