docs: start milestone v1.2 Multi-Provider, Theming & Zero-Setup
This commit is contained in:
+18
-3
@@ -16,9 +16,24 @@ v1.1 turned the v1.0 MVP into a configurable, administrable, maintainable app: g
|
||||
|
||||
Deferred to backlog: self-service provider onboarding (999.5), provider abstraction (999.1), dark mode / theming (999.20), and a broader modern-styling refresh (999.21 — future milestone).
|
||||
|
||||
## Next Milestone
|
||||
## Current Milestone: v1.2 Multi-Provider, Theming & Zero-Setup
|
||||
|
||||
Not yet defined. Start with `/gsd-new-milestone` (questioning → research → requirements → roadmap). Candidate seeds in the backlog: dark mode / theming (999.20), modern visual refresh (999.21), self-service onboarding (999.5), provider abstraction (999.1), dev-user full-app exercise without a real calendar (999.19), and acting on the CI dependency report (999.18).
|
||||
**Goal:** Open FamilySync beyond Fastmail — add Google Calendar as a first-class provider behind a provider-abstraction layer with self-service per-provider onboarding — plus dark mode, multiple reminders per event, and a database that bootstraps itself with no manual setup.
|
||||
|
||||
**Target features:**
|
||||
|
||||
- **Provider abstraction** — refactor Fastmail behind a provider interface so additional calendar providers plug in cleanly (999.1).
|
||||
- **Gmail / Google Calendar, full parity** — read + write-back + reminders via the Google Calendar API + OAuth2 (not CalDAV); the second provider behind the abstraction.
|
||||
- **Self-service onboarding, per-provider native flow** (999.5, pivoted to generic provider) — Fastmail = app-password entry, Gmail = "Connect Google" OAuth button; low-friction for the non-technical Apple member.
|
||||
- **Multiple reminders per event** — multiple VALARMs per event (deferred to v1.2 from v1.1).
|
||||
- **PWA dark mode / theming** (999.20) — light/dark/system switch consuming the Phase 17 semantic-token groundwork.
|
||||
- **Zero-manual-setup DB** — auto-create/migrate tables on boot if missing (bring-your-own MariaDB: creds + DB name → working schema), then the existing setup wizard handles admin + config.
|
||||
- **Dev-user full-app exercise** (999.19) — exercise the whole app without a real calendar connected.
|
||||
- **Act on CI dependency report** (999.18) — apply the outdated/vulnerable dependency updates CI surfaces.
|
||||
|
||||
**Explicitly out of this milestone:** modern visual refresh (999.21 stays in backlog — current UX is satisfactory). v1.3 is reserved for tablet/touchscreen UX.
|
||||
|
||||
Phase numbering continues from v1.1 (last phase 20) → v1.2 starts at Phase 21.
|
||||
|
||||
## Requirements
|
||||
|
||||
@@ -127,4 +142,4 @@ This document evolves at phase transitions and milestone boundaries.
|
||||
|
||||
---
|
||||
|
||||
_Last updated: 2026-06-18 after v1.1 milestone — Operability & Polish shipped (Phases 7–20, 57 plans): guided setup, in-app admin + member editor, per-event reminders, faster write-back, local-auth mode, auto timezone, and full Gitea CI/CD. Next milestone undefined — start with `/gsd-new-milestone`._
|
||||
_Last updated: 2026-06-19 — v1.2 milestone started (Multi-Provider, Theming & Zero-Setup): provider abstraction + Gmail full parity, self-service per-provider onboarding, multiple reminders per event, PWA dark mode, zero-manual-setup DB bootstrap, dev-user full-app exercise, and CI dependency updates. Phases continue from 21._
|
||||
|
||||
+13
-17
@@ -1,20 +1,16 @@
|
||||
---
|
||||
gsd_state_version: 1.0
|
||||
milestone: v1.1
|
||||
milestone_name: Operability & Polish
|
||||
current_phase: null
|
||||
status: Awaiting next milestone
|
||||
stopped_at: v1.1 milestone shipped & archived
|
||||
last_updated: "2026-06-19T01:58:30.566Z"
|
||||
last_activity: 2026-06-18
|
||||
last_activity_desc: Milestone v1.1 completed and archived
|
||||
milestone: v1.2
|
||||
milestone_name: Multi-Provider, Theming & Zero-Setup
|
||||
status: planning
|
||||
last_updated: "2026-06-19T13:13:25.671Z"
|
||||
last_activity: 2026-06-19
|
||||
progress:
|
||||
total_phases: 20
|
||||
completed_phases: 20
|
||||
total_plans: 57
|
||||
completed_plans: 57
|
||||
percent: 100
|
||||
current_phase_name: Awaiting next milestone
|
||||
total_phases: 0
|
||||
completed_phases: 0
|
||||
total_plans: 0
|
||||
completed_plans: 0
|
||||
percent: 0
|
||||
---
|
||||
|
||||
# Project State
|
||||
@@ -28,10 +24,10 @@ See: .planning/PROJECT.md (updated 2026-06-18 after v1.1 milestone)
|
||||
|
||||
## Current Position
|
||||
|
||||
Phase: Milestone v1.1 complete
|
||||
Phase: Not started (defining requirements)
|
||||
Plan: —
|
||||
Status: Awaiting next milestone
|
||||
Last activity: 2026-06-19 — Milestone v1.1 completed and archived
|
||||
Status: Defining requirements
|
||||
Last activity: 2026-06-19 — Milestone v1.2 started
|
||||
|
||||
### ✅ Resolved Checkpoint — Phase 15 Plan 15-03 Task 2 (human-action)
|
||||
|
||||
|
||||
Reference in New Issue
Block a user