Phillip Tarrant
53e62f694f
Remove phase implementation plans, design notes, and source spreadsheet that are no longer needed. Add architecture.md, API_REFERENCE.md, and database_schema.md for ongoing development and debugging reference. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
1.4 KiB
SneakySwole Roadmap
Completed
Phase 1: Scaffold & Infrastructure
FastAPI project structure, Dockerfile + docker-compose.yaml, Pico CSS dark theme base template, .env config, structlog logging, health check endpoint.
Phase 2: Data Layer & Seeding
8-table SQLite schema via SQLModel + Alembic migrations. YAML-driven seed script (config/exercises.yaml, config/user_programs.yaml). Service layer for all DB access. Admin user auto-created from .env with bcrypt.
Phase 3: Workout UI
Admin login (bcrypt + signed session cookies), profile switcher, workout day viewer with warmups and exercise cards, HTMX-powered exercise browser with search/filter. NavContextMiddleware for automatic template context.
Phase 4: Logging & Tracking
Inline set logging from the workout day view via HTMX. Auto-created workout sessions. Log history with per-session detail view. Edit and delete log entries.
Phase 5: Progression & Analytics
Auto-progression engine (+reps/+weight/deload rules), 4-week schedule calendar, progress dashboard with Chart.js charts, per-exercise progress pages with suggestions.
Future Ideas
- Multi-user login (replace profile switcher with individual logins)
- REST API for mobile clients
- Exercise video/image attachments
- Custom workout program builder
- Export/import workout data (CSV/JSON)
- Notifications/reminders
- Social features (sharing workouts)