From 557eec953bd5a7566d04d0d96f7f0da29c1b58c1 Mon Sep 17 00:00:00 2001 From: Dave Date: Tue, 22 Sep 2026 21:47:11 +0200 Subject: [PATCH] Document work area workflow and schema setup --- README.md | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+) diff --git a/README.md b/README.md index ce41f77..f2b035e 100644 --- a/README.md +++ b/README.md @@ -114,6 +114,25 @@ optional `projects.plan_data` JSON field; it does not run the full setup script or rewrite existing records. Existing projects start with an empty draft, and no existing card dates are overwritten. +## Work areas + +Each project has its own named work areas. A card can link to one area while +keeping its independent Kanban column, priority, and plan dates. The board +shows an area-colored edge and label on linked cards; the area legend filters +the visible cards. The Plan page shows the same area labels alongside its +existing priority-colored schedule bars. Existing cards remain uncategorised +until assigned on their card page. + +The quick-add and intake forms ask for an existing area or a new name. New +areas receive the next unused color from a fixed palette; the color is saved +on the area record. `work_areas` is related to `projects`, and client reads +follow the project's client access rule. Client writes are validated by the +app before using the admin connection. + +Run `npm run setup-work-area-schema` with `.env.local` loaded to add only the +`work_areas` collection and optional `cards.work_area` relation. The same +schema addition is included in `npm run setup-remote` for new environments. + ## Specs and plans - `docs/superpowers/specs/` — design documents