Files

T

kawaandClaude Sonnet 4.6 a26608791f chore: complete v1.3 milestone — Backend Expansion

Archives v1.3 milestone (Phase 13: 18 rclone backends), updates PROJECT.md
with all 30 validated requirements, reorganizes ROADMAP.md with all 4 milestones
in collapsed details blocks, adds v1.2 and v1.3 retrospective entries.

Also commits minor CSS token fixes in src/ (text-on-surface-container class
alignment) that were uncommitted from phase 13 execution.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

2026-04-16 16:54:45 +02:00

9.4 KiB

Raw Blame History

Roadmap: Ready2Blob

Milestones

✅ v1.0 MVP — Phases 1–4 (shipped 2026-03-27)
✅ v1.1 Backlog & Tech Debt — Phases 5–7 (shipped 2026-03-31)
✅ v1.2 UI Polish & Clarity — Phases 8–12 (shipped 2026-04-01)
v1.3 Backend Expansion — Phase 13 (in progress)

Phases

✅ v1.0 MVP (Phases 1–4) — SHIPPED 2026-03-27

Phase 1: Foundation (4/4 plans) — completed 2026-03-26
Phase 2: Generators (4/4 plans) — completed 2026-03-26
Phase 3: Wizard UI (5/5 plans) — completed 2026-03-27
Phase 4: Review, Download & Security (5/5 plans) — completed 2026-03-27

Full phase details: .planning/milestones/v1.0-ROADMAP.md

✅ v1.1 Backlog & Tech Debt (Phases 5–7) — SHIPPED 2026-03-31

Phase 5: Tech Debt (4/4 plans) — completed 2026-03-30
Phase 6: New Backends (4/4 plans) — completed 2026-03-31
Phase 7: Validation & UX Polish (3/3 plans) — completed 2026-03-31

Full phase details: .planning/milestones/v1.1-ROADMAP.md

✅ v1.2 UI Polish & Clarity (Phases 8–12) — SHIPPED 2026-04-01

Phase 8: Theme Foundation - MD3 color token system and dark mode infrastructure (completed 2026-04-01)
Phase 9: MD3 Components - UI primitives and component migration to semantic tokens (completed 2026-04-01)
Phase 10: Content & Clarity - Intro section, step descriptions, and contextual help (completed 2026-04-01)
Phase 11: Polish & Responsiveness - Mobile layout, focus states, transitions, scroll-to-error (completed 2026-04-01)
Phase 12: Dark mode visibility fixes - Fix dark mode regressions (completed 2026-04-01)

v1.3 Backend Expansion (In Progress)

Milestone Goal: Expand backend support from 7 to 17 rclone backends with categorized selection, search filtering, OAuth token-paste guidance, and inline icons.

Phase Details

Phase 8: Theme Foundation

Goal: App has a complete MD3 color token system and working dark mode toggle with no flash of unstyled content Depends on: Phase 7 (v1.1 complete) Requirements: THEME-01, THEME-02 Success Criteria (what must be TRUE):

All color values in the app flow from CSS custom properties defined in a single token file, not from hardcoded Tailwind color classes
User can toggle between System, Light, and Dark themes via a visible control, and the entire UI responds immediately
Theme preference persists in localStorage and applies on reload without any flash of wrong theme
Tailwind v4 @theme directive maps MD3 token names to utility classes (e.g., bg-surface, text-on-primary) Plans: 2/2 plans complete Plans:

08-01-PLAN.md — Token system, flash prevention, ThemeToggle component
08-02-PLAN.md — Color class migration across all components

Phase 9: MD3 Components

Goal: All interactive elements use MD3-styled primitives with consistent visual language across the entire wizard Depends on: Phase 8 Requirements: COMP-01, COMP-02, COMP-03, COMP-04, DEBT-01 Success Criteria (what must be TRUE):

Text inputs render as outlined fields with floating labels that animate on focus and when the field has content
Buttons visually distinguish primary (filled), secondary (outlined), and tertiary (text) actions across all wizard steps
Backend selection cards and output blocks display MD3 elevation with tonal surface tint and consistent shape tokens
Step indicator shows numbered circles connected by lines, with checkmarks on completed steps, highlight on current, and muted future steps
FieldRenderer produces identical aria-label attributes for both text-branch and select-branch inputs Plans: 5/5 plans complete Plans:

09-01-PLAN.md — TextFieldMD3 component, MD3 button constants, DEBT-01 aria-label fix
09-02-PLAN.md — StepIndicator rebuild with MD3 circles and connectors
09-03-PLAN.md — Integration: wire TextFieldMD3 + button styles + elevation into all wizard steps
09-04-PLAN.md — Gap closure: Replace BackendSelectionStep plain input with TextFieldMD3
09-05-PLAN.md — Gap closure: Tooltip hover behavior + icon placement beside helpText

Phase 10: Content & Clarity

Goal: A first-time visitor understands what Ready2Blob does and what each wizard step expects without external documentation Depends on: Phase 8 (tokens needed for consistent styling of new content) Requirements: UX-01, UX-02, UX-03, UX-04 Success Criteria (what must be TRUE):

Landing view shows an intro section explaining what Ready2Blob does with a clear call-to-action to start the wizard
Remote name field displays a placeholder example, help text, and a live preview showing how the name appears in [remote-name] config syntax
Every wizard step has a 1-2 sentence description below the heading explaining what the user is doing and why
All backend credential fields have contextual help text explaining what to enter and where to find the value Plans: 3/3 plans complete Plans:

10-01-PLAN.md — Intro section with CTA and step descriptions for all 4 steps
10-02-PLAN.md — Remote name live config preview with helpText
10-03-PLAN.md — Credential field tooltipText and helpText enrichment

Phase 11: Polish & Responsiveness

Goal: The wizard feels production-ready on any device with smooth interactions and accessible keyboard navigation Depends on: Phase 9, Phase 10 Requirements: POLISH-01, POLISH-02, POLISH-03, POLISH-04 Success Criteria (what must be TRUE):

On a mobile viewport (< 640px), backend cards stack vertically, form fields span full width, step indicator collapses, and buttons stretch to fill width
Every interactive element shows a visible 3px MD3 focus outline when navigated via keyboard (using focus-visible)
Step transitions use a subtle fade/slide animation that is suppressed when the user has prefers-reduced-motion enabled
When form validation fails, the view auto-scrolls to the first field with an error Plans: 2/2 plans complete Plans:

11-01-PLAN.md — Mobile responsive layout + MD3 focus-visible indicators
11-02-PLAN.md — Step transition animation + auto-scroll to first error

Phase 12: Dark mode visibility fixes

Goal: Fix dark mode visibility regressions where step headings, DeploymentStep form controls, and FieldRenderer select elements are invisible or unstyled against the dark background Requirements: DARK-01, DARK-02, DARK-03 Depends on: Phase 11 Success Criteria (what must be TRUE):

All wizard step h2 headings are readable in dark mode with proper contrast
DeploymentStep labels, legends, checkboxes, and radios are visible and styled in dark mode
FieldRenderer select element has proper background and text color in dark mode Plans: 2/2 plans complete

Plans:

12-01-PLAN.md — Fix step headings, DeploymentStep form controls, ReviewStep checkbox
12-02-PLAN.md — Fix FieldRenderer select dark mode styling

Phase 13: Add remaining RClone remotes

Goal: Expand backend support from 7 to 17 rclone backends with categorized selection UI, instant search, OAuth token-paste guidance, and inline SVG icons — covering all backends suitable for unattended Windows deployment Requirements: REMOTE-01, REMOTE-02, REMOTE-03, REMOTE-04, REMOTE-05, REMOTE-06 Depends on: Phase 12 Success Criteria (what must be TRUE):

BACKEND_REGISTRY contains 17 backends with correct fields, categories, and rclone type mappings
BackendType is derived from registry keys (not an explicit union)
BackendSelectionStep groups backends by category with instant search and inline SVG icons
OAuth-token backends show collapsible OAuthInstructions with backend-specific rclone authorize command
RemoteConfigStep renders correct form for every backend including GdriveAuthToggle
buildRcloneConf produces valid rclone.conf for all 17 backends Plans: 4/4 plans complete