From 7b4f50f9531f80d377a06df3c5f49ab418ad2a86 Mon Sep 17 00:00:00 2001 From: Arthur Belleville Date: Sat, 16 May 2026 10:52:10 +0200 Subject: [PATCH] docs: start milestone v3.0 Design System & Visual Polish --- .planning/PROJECT.md | 41 +++++++++++++++++++++++++---------------- .planning/STATE.md | 29 ++++++++++++++--------------- 2 files changed, 39 insertions(+), 31 deletions(-) diff --git a/.planning/PROJECT.md b/.planning/PROJECT.md index 1bc21c9..1d9885d 100644 --- a/.planning/PROJECT.md +++ b/.planning/PROJECT.md @@ -2,7 +2,7 @@ ## What This Is -A Go + HTMX version of Xtablo centered on tablos as collaborative workspaces. v1 established the authenticated Tablos workflow with tasks, files, worker, and deploy scaffolding; v2 adds the collaboration and planning layer around each tablo: native messaging, etapes, scheduled events, personal planning, and Google/Apple sign-in. +A Go + HTMX version of Xtablo centered on tablos as collaborative workspaces. v1 established the authenticated Tablos workflow with tasks, files, worker, and deploy scaffolding; v2 added collaboration, messaging, etapes, events, planning, and Google sign-in; v3 replaces the minimal backend UI with a full design system that makes the product look like the existing JS app. Built for a developer who wants a simpler, durable product stack: one Go server, Postgres, server-rendered UI, and no managed chat provider. @@ -12,15 +12,16 @@ Built for a developer who wants a simpler, durable product stack: one Go server, If everything else fails, this must work end-to-end on a single Go binary backed by Postgres and an S3-compatible bucket. -## Current Milestone: v2.0 Collaboration, planning, and social sign-in +## Current Milestone: v3.0 Design System & Visual Polish -**Goal:** Add the collaboration and scheduling capabilities that make tablos useful for ongoing work, while keeping the Go+HTMX/server-owned architecture. +**Goal:** Replace the minimal backend UI layer with a full design system ported from `go-backend/internal/web/ui`, then apply it to every surface using the JS app as the visual reference. **Target features:** -- Native per-tablo chat/messaging with real-time delivery, persisted in Postgres, and no third-party chat vendor -- Etapes as one-level wrappers around tasks: a task may belong to one etape, and an etape cannot itself have a parent -- Google and Apple sign-in flows integrated into the existing server-managed session model -- Individual planning view for each authenticated user, including scheduled events that belong to tablos like tasks do +- Design system foundation: port CSS tokens and component library (button, input, card, badge, modal, select, textarea, table, empty-state) into `backend/internal/web/ui` +- Auth pages (login/signup) restyled to match the JS product visual +- Dashboard & Tablos (sidebar, tablo list, project cards) restyled +- Tablo detail (tasks/kanban, etapes, files) restyled +- Chat & Planning pages restyled ## Requirements @@ -28,18 +29,26 @@ If everything else fails, this must work end-to-end on a single Go binary backed -(None yet — ship to validate) +- ✓ Server-managed sessions with email/password auth — Phase 2 (v1.0) +- ✓ Tablos CRUD with ownership — Phase 3 (v1.0) +- ✓ Tasks kanban with drag-and-drop reorder — Phase 4 (v1.0) +- ✓ File attachments with orphan cleanup worker — Phases 5–6 (v1.0) +- ✓ Single-binary production deploy with Caddy TLS — Phase 7 (v1.0) +- ✓ Google sign-in (server-managed sessions) — Phase 8 (v2.0) +- ✓ Etapes as one-level task wrappers — Phase 9 (v2.0) +- ✓ Tablo events with CRUD — Phase 10 (v2.0) +- ✓ Individual planning view (`/planning`) — Phase 11 (v2.0) +- ✓ Native per-tablo chat with real-time SSE — Phase 12 (v2.0) ### Active - + -- [ ] Existing users can continue using email/password sessions while new users can sign in with Google or Apple -- [ ] Tablo detail pages support native discussions/messages persisted in Postgres -- [ ] Real-time message delivery works without a managed messaging provider -- [ ] Users can organize tasks under one-level etapes inside a tablo -- [ ] Users can create, edit, view, and delete scheduled events attached to tablos -- [ ] Each authenticated user has an individual planning view aggregating their events +- [ ] A full design system (tokens + component library) lives in `backend/internal/web/ui` and can be used by all templates +- [ ] Auth pages look visually equivalent to the JS app (login/signup) +- [ ] Dashboard and tablo list match the sidebar + project-card layout from the JS app +- [ ] Tablo detail (tasks, etapes, files) matches the JS app's visual treatment +- [ ] Chat and planning views have consistent, polished styling ### Out of Scope @@ -117,4 +126,4 @@ This document evolves at phase transitions and milestone boundaries. - **Milestone v2.0 started: Collaboration, planning, and social sign-in** — Started 2026-05-15. Scope: native per-tablo chat, one-level etapes, Google/Apple sign-in, and individual planning with tablo events. --- -*Last updated: 2026-05-15 after starting milestone v2.0* +*Last updated: 2026-05-16 after starting milestone v3.0* diff --git a/.planning/STATE.md b/.planning/STATE.md index 575db98..b5e9514 100644 --- a/.planning/STATE.md +++ b/.planning/STATE.md @@ -1,16 +1,16 @@ --- gsd_state_version: 1.0 -milestone: v2.0 -milestone_name: Collaboration, planning, and social sign-in -status: executing -last_updated: "2026-05-16T08:33:45.416Z" -last_activity: 2026-05-16 -- Phase 12 execution complete +milestone: v3.0 +milestone_name: Design System & Visual Polish +status: planning +last_updated: "2026-05-16T08:52:04.598Z" +last_activity: 2026-05-16 progress: - total_phases: 5 - completed_phases: 5 - total_plans: 18 - completed_plans: 18 - percent: 100 + total_phases: 0 + completed_phases: 0 + total_plans: 0 + completed_plans: 0 + percent: 0 --- # STATE @@ -28,11 +28,10 @@ See: `.planning/PROJECT.md` (updated 2026-05-15) ## Current Position -Phase: 12 -Plan: 03 complete -Status: Complete -Last activity: 2026-05-16 -- Phase 12 execution complete -Resume file: .planning/phases/12-native-tablo-chat/12-03-SUMMARY.md +Phase: Not started (defining requirements) +Plan: — +Status: Defining requirements +Last activity: 2026-05-16 — Milestone v3.0 started ## Phase Status