docs: update roadmap, feature parity, and readme through phase 5
This commit is contained in:
+5
-5
@@ -128,7 +128,7 @@
|
||||
|
||||
---
|
||||
|
||||
## Phase 5 — Guilded Signature Features 🔄 IN PROGRESS
|
||||
## Phase 5 — Guilded Signature Features ✅ COMPLETE
|
||||
|
||||
> The features that set Guilded apart: calendar, docs, lists, scheduling.
|
||||
|
||||
@@ -137,7 +137,7 @@
|
||||
| 5.1 | Calendar Channels | ✅ Events, RSVPs, month grid |
|
||||
| 5.2 | Docs Channels | ✅ CRUD, wiki sidebar, markdown editor |
|
||||
| 5.3 | Lists Channels | ✅ TODO/DOING/DONE columns, CRUD |
|
||||
| 5.4 | Scheduling / Availability | Pending |
|
||||
| 5.4 | Scheduling / Availability | ✅ DB, API, UI in server settings |
|
||||
|
||||
### 5.1 Calendar Channels
|
||||
- **Backend:** New `calendar` channel type. New `events` table (channel_id, creator_id, title, description, start_time, end_time, recurrence_rule, location, color). New `event_rsvps` table (event_id, user_id, status: going/maybe/no, responded_at).
|
||||
@@ -153,9 +153,9 @@
|
||||
- **Estimated:** 3 files backend, 2 files frontend.
|
||||
|
||||
### 5.3 Lists Channels (Task Management)
|
||||
- **Backend:** New `list` channel type. New `list_items` table (channel_id, creator_id, title, description, assignee_id, due_date, status: todo/in_progress/done, position, completed_at). Supports nested items (parent_id).
|
||||
- **Route:** CRUD for list items. Bulk status update. Filter by assignee/status.
|
||||
- **Frontend:** Lists channel renders as a kanban board or checklist view. Drag-and-drop reordering. Assignee avatars, due date badges, status filters.
|
||||
- **Backend:** New `list` channel type. New `list_items` table (channel_id, creator_id, title, status: todo/in_progress/done, position). Minimal CRUD: create item, update title/status, delete.
|
||||
- **Route:** CRUD for list items.
|
||||
- **Frontend:** 3-column kanban view (TODO/DOING/DONE). Add items inline, click checkbox to cycle status, delete on hover.
|
||||
- **Estimated:** 3 files backend, 3 files frontend.
|
||||
|
||||
### 5.4 Scheduling / Availability
|
||||
|
||||
Reference in New Issue
Block a user