Moheeb Zara
8edc9da611
Finalizes the docs section after an adversarial audit (code review + per-page fact-check + coherence critic) and two content requests. - Accuracy: fixed 10 invented cross-link slugs, the admin-vs-board gating claims the verifiers caught (permissions matrix, /settings, invites, onboarding, connect-payments, proposal withdraw, Stripe reconciliation, member fields, door.operate), and 2 issues in the new pages (project area-at-creation, forum thread-delete role). - Coverage: added 5 how-to pages so every module is documented (recurring Stripe dues, tasks & chores, projects, comms & forum, ops knowledge base + secrets vault). 34 pages total. - Screenshots: 12 captioned app screenshots under public/docs-media/, embedded as figures. Each tutorial now has 2-3 step screenshots. - Style: removed all em-dashes/en-dashes/ellipses from the docs (natural ASCII punctuation). - Handoff (docs/HANDOFF-audit-cleanup.md) updated with the current state. typecheck 0 · lint 0 errors · build ok (all 34 /docs pages prerendered)
57 lines
3.5 KiB
Markdown
57 lines
3.5 KiB
Markdown
The [/tasks](/tasks) screen (Tasks & Chores) is the shared to-do list for your space: one-off jobs, recurring upkeep, and the open pool that anyone can claim. This recipe covers creating tasks and chores, claiming and completing them, and where they surface.
|
|
|
|
|
|
|
|
## Before you start
|
|
|
|
Creating, claiming, completing, and deleting tasks is not a permission-gated action. Any active member (status `current`, `late`, or `unverified`) can do all of it, so this screen works even for members still pending approval. There is no separate manager role for the task list.
|
|
|
|
Area tags come from the areas you defined for your space. If you have not set those up yet, see [Customize your space](/docs/how-to/customize-space); until then the form falls back to a built-in default list (3D Printing, Electronics, Woodshop, Laser, Metal Shop, Facilities, Admin, Kitchen, General).
|
|
|
|
## Create a one-off task
|
|
|
|
1. Open [/tasks](/tasks) and click **New Task** (top right).
|
|
2. Enter a **Title** (required, up to 200 characters) and an optional **Description**.
|
|
3. Leave **Type** set to `Task` for a normal one-off job.
|
|
4. Optionally pick an **Area** and a **Due Date**.
|
|
5. Leave **Recurrence** on `none`.
|
|
6. Click **Create Task**.
|
|
|
|
The task is created with status `open` and records you as the requester. It joins the open pool for anyone to claim. The create form does not include an assignee, so tasks are claimed rather than handed out; the "assigned to" label only appears on tasks that already carry an assignee.
|
|
|
|
## Create a recurring chore
|
|
|
|
1. Click **New Task** and fill in the title as above.
|
|
2. Set **Type** to `Chore` to mark it as routine upkeep.
|
|
3. Set **Recurrence** to `daily`, `weekly`, `biweekly`, or `monthly`.
|
|
4. Optionally set an **Area** and **Due Date**, then click **Create Task**.
|
|
|
|
Any recurrence other than `none` moves the item to the **Ongoing** tab and it displays as, for example, "weekly recurring".
|
|
|
|
## Claim and complete work
|
|
|
|
1. On an `open` task, click **CLAIM**. The status becomes `claimed` and your name shows as the claimer.
|
|
2. When the work is finished, click **DONE** on a task you claimed. The status becomes `completed` and the completion time is recorded (this also stamps `last_done_at`, so recurring chores keep a record of when they were last done).
|
|
|
|
You can only mark **DONE** on tasks you claimed yourself. Use the **X** on any row to delete a task.
|
|
|
|
## The tabs and statuses
|
|
|
|
The [/tasks](/tasks) screen has four tabs:
|
|
|
|
- **Open Tasks**: open, non-recurring items in the pool.
|
|
- **Ongoing**: open recurring chores.
|
|
- **My Tasks**: open tasks claimed by or assigned to you.
|
|
- **Done**: completed items.
|
|
|
|
The underlying `task_status` values are `open`, `claimed`, `in_progress`, `overdue`, `due_today`, `completed`, `done`, and `blocked`. Creating sets `open`, claiming sets `claimed`, and completing sets `completed`; the remaining values (`in_progress`, `blocked`, and the date-driven `overdue` / `due_today`) are used for display and reporting.
|
|
|
|
## Where tasks appear
|
|
|
|
Open tasks also surface on your [/dashboard](/dashboard): the **Quick Chores** widget lists open items with a **CLAIM** shortcut, and the **Open Tasks** stat shows the current count plus how many are overdue. The **Quick Task** button jumps straight to [/tasks](/tasks).
|
|
|
|
## Related
|
|
|
|
- [Customize your space](/docs/how-to/customize-space) to define the areas used as task tags.
|
|
- [Getting started](/docs/tutorials/getting-started) for a tour of the rest of the platform.
|