43 Commits

Author	SHA1	Message	Date
Lars	f1ee1eec7e	feat: update maturity models and version to 0.7.2 ... - Incremented application version to 0.7.2 and updated database schema version to 20260427025. - Enhanced maturity models functionality to support M:N relationships for focus areas, style directions, and target groups. - Updated frontend to allow multi-selection for focus areas, style directions, and target groups. - Documented changes in the changelog for version 0.7.2, including new migration details and UI improvements.	2026-04-27 11:42:03 +02:00
Lars	5277f4f4cf	feat: add maturity models functionality and update version ... - Introduced new maturity models feature with CRUD operations in the API. - Added routes and frontend components for managing maturity models. - Updated version to 0.7.1 with corresponding build date and schema version. - Enhanced admin navigation to include maturity models section. - Documented changes in the changelog for version 0.7.1.	2026-04-27 11:32:30 +02:00
Lars	c738f1234b	fix: MediaWiki import - increase limit to 500 and add validation ... Error: 422 Unprocessable Entity when limit > 100 Root cause: Backend enforced max=100, frontend allowed any value Backend fix: - Increased preview limit from 100 to 500 (consistent with execute) - import_wiki.py line 64: le=100 → le=500 Frontend fix: - Added Math.min/max validation to both limit inputs - Preview limit: max 500 with auto-clamp - Execute limit: max 500 with auto-clamp - Updated placeholder: 'Kein Limit (max 500)' Prevents 422 errors from invalid limit values	2026-04-24 17:15:17 +02:00
Lars	89055ddbc4	feat: Admin page navigation with MediaWiki Import link ... - New AdminPageNav component with horizontal navigation - Links to Hierarchie / Kataloge / Wiki-Import - Integrated in all 3 admin pages - Uses lucide-react icons (TreePine, FolderTree, Download) - Active state tracking via useLocation - Mobile-friendly with flexbox layout Navigation flow: /admin/hierarchy → /admin/catalogs → /admin/mediawiki-import	2026-04-24 17:03:13 +02:00
Lars	46d000d6b3	feat: SMW-Importer Frontend (Phase 2 complete) ... Phase 2A: API Functions - 5 MediaWiki import functions in api.js - previewMediaWikiImport, executeMediaWikiImport - getMediaWikiImportStatus, listMediaWikiImportLogs - deleteMediaWikiImportReference Phase 2B: UI Component - MediaWikiImportPage.jsx (3-tab interface) - Preview Tab: Category selection, preview with accordions - Execute Tab: Import form with status polling - History Tab: Import log list with refresh Phase 2C: Routing - Added /admin/mediawiki-import route in App.jsx - Import and ProtectedRoute wrapper Issue: SMW-Importer Frontend (Option C from handover) Related: backend/routers/csv_import.py (MediaWiki endpoints)	2026-04-24 16:06:49 +02:00
Lars	e80c8e01e1	fix: add listTrainingStyles alias for backward-compatibility (references listStyleDirections)	2026-04-24 15:20:39 +02:00
Lars	0e0b709768	refactor: split AdminHierarchyPage into modular components ... Split 1200+ line file into clean modular architecture: - FocusAreaNode.jsx - Tree nodes with nested style directions + training types - HierarchyTab.jsx - Tab 1 with tree view and detail panel - CatalogsTab.jsx - Tab 2 with global catalogs (Target Groups, Skill Categories, Training Characters) - AssignmentsTab.jsx - Tab 3 with M:N checkbox matrix (Style Directions ↔ Target Groups) - DetailPanel.jsx - All edit forms (Focus Area, Style Direction, Training Type) + create forms Fixes ESBuild parser error from large file size. Implements full CRUD: create, edit, delete, reassign focus areas. Responsive design with mobile/desktop layouts.	2026-04-24 09:08:12 +02:00
Lars	9ec1cf7781	fix: temporarily use simple admin hierarchy to fix build ... Large AdminHierarchyPage.jsx (1200+ lines) causes ESBuild parser error. Using simplified version temporarily while investigating the issue. Broken version saved as AdminHierarchyPage.broken.jsx for debugging. Will split into modules and restore full functionality.	2026-04-24 08:57:13 +02:00
Lars	af2fc31f70	fix: build error - remove dynamic template from style tag	2026-04-24 08:52:12 +02:00
Lars	3fda149049	feat: complete admin system - global catalogs + M:N assignments ... Tab System: - Tab 1: Hierarchie (Fokusbereich → Stilrichtung/Trainingstyp) - Tab 2: Kataloge (Zielgruppen, Fähigkeiten, Trainingscharakter) - Tab 3: Zuordnungen (Matrix Stilrichtungen ↔ Zielgruppen) Global Catalogs (Tab 2): - Zielgruppen: CRUD mit Altersangaben (zentral verwaltet) - Fähigkeitskategorien: CRUD (global) - Trainingscharakter: CRUD (global) - Reusable CatalogSection component with dynamic fields - Create/Edit/Delete für alle Kataloge - Inline editing + validation M:N Assignments Matrix (Tab 3): - Checkbox-Grid: Stilrichtungen (Zeilen) × Zielgruppen (Spalten) - Grouped by Focus Area for clarity - Toggle assignments with immediate save - Shows empty states with helpful messages - Fully responsive table with horizontal scroll Architecture: - Trainingstypen: Context-specific per focus area (create new) - Zielgruppen: Global catalog (assign via matrix) - Clean separation of concerns - Proper loading states + error handling Mobile responsive across all tabs. Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>	2026-04-24 08:46:32 +02:00
Lars	80986735b5	feat: complete admin hierarchy - create + reassign functions ... Create Functions: - '+ Neu' buttons for Style Directions and Training Types - Create forms with focus area context - Auto-assigns to parent focus area - Loading states + validation Reassignment: - Focus area dropdown in edit forms - Move style directions between focus areas - Move training types between focus areas - Updates hierarchy immediately after save Full CRUD now complete: - Create: new elements under focus area - Read: tree view with nested elements - Update: edit + reassign to different focus area - Delete: with confirmation dialogs Mobile + Desktop responsive design maintained. Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>	2026-04-24 08:39:48 +02:00
Lars	af89546022	feat: complete admin hierarchy - edit/delete + responsive design ... Features: - Edit forms for Style Directions and Training Types (working) - Delete functions with confirmation dialogs - Responsive layout: mobile (stacked), tablet/desktop (side-by-side) - Back button on mobile to return to tree view - Full CRUD except create (can use old catalogs page for now) Mobile UX: - Tree view fills screen - Click item → detail panel replaces tree - Back button → return to tree - Safe bottom padding for navigation Desktop UX: - 400px tree + fluid detail panel - Both always visible - No back button (not needed) Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>	2026-04-24 08:33:11 +02:00
Lars	599d696321	fix: add getAdminHierarchy to api export object	2026-04-24 08:25:03 +02:00
Lars	7314ae1436	feat: Hierarchical Admin UI - Tree View for Catalogs ... Backend: - New endpoint: GET /api/admin/hierarchy - Returns hierarchical structure: Focus Areas with nested Style Directions + Training Types - Style Directions include target_groups assignments (M:N) - JSON aggregation for efficient data loading Frontend: - New page: AdminHierarchyPage.jsx with Tree + Detail Panel layout - Tree View: Expandable/collapsible nodes (Focus Areas → Stilrichtungen/Trainingstypen) - Detail Panel: Shows selected item details, inline editing - Visual hierarchy: Icons, indentation, color coding - Responsive layout: Fixed 400px tree, fluid detail panel Routes: - /admin now redirects to /admin/hierarchy (new default) - /admin/hierarchy: Tree-based catalog management - /admin/catalogs: Legacy flat UI (still available) UX Improvements: - Visual hierarchy instead of flat tabs - M:N relationships visible (target groups per style) - Better navigation: Click to select, expand/collapse sections - Cleaner layout: Two-column design Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>	2026-04-24 07:51:40 +02:00
Lars	fe5d29e40e	feat: Training Types → Focus Area Hierarchie ... Migration 013: - Adds focus_area_id to training_types (context-specific types) - Migrates existing data to Karate focus area - Seeds focus-area-specific training types: * Karate: Dan-Vorbereitung * Gewaltschutz: Präventivkurse, Intensivtraining, Spezialkurse * Fitness: Gesundheitssport, Funktionelles Training - Updates unique constraint to (name, focus_area_id) Backend (catalogs.py): - list_training_types: Added focus_area_id filter, LEFT JOIN focus_areas - create_training_type: Added focus_area_id parameter - update_training_type: Added focus_area_id parameter - Enriched responses with focus_area_name and focus_area_icon Frontend (AdminCatalogsPage): - Added Fokusbereich dropdown to create form - Added Fokusbereich dropdown to edit form - Display shows focus_area_icon and focus_area_name - Training types now context-specific to focus areas Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>	2026-04-23 15:29:23 +02:00
Lars	9f44cff77b	fix: Stilrichtungen → Fokusbereich Zuordnung (focus_area_id) ... Problem: Stilrichtungen-Tab zeigte falsches Feld 'Übergeordneter Stil' (parent_style_id) Lösung: Fokusbereich-Dropdown (focus_area_id) für Hierarchie Backend (catalogs.py): - INSERT: focus_area_id Parameter hinzugefügt - UPDATE: focus_area_id Parameter hinzugefügt - SELECT: LEFT JOIN focus_areas für focus_area_name + icon - Response enriched mit focus_area_name/icon Frontend (AdminCatalogsPage.jsx): - newTS State: parent_style_id → focus_area_id - Create Form: Fokusbereich-Dropdown statt 'Übergeordneter Stil' - Edit Form: Fokusbereich-Dropdown mit focusAreas - Display: Zeigt Fokusbereich-Icon + Name (accent color) - parent_style_id bleibt für optionale Stil-Hierarchien Jetzt kann Hierarchie korrekt angelegt werden: ✅ Karate → Goju-Ryu ✅ Karate → Shotokan ✅ Gewaltschutz → (eigene Stilrichtungen) version: 0.5.0 module: catalogs 1.5.0, AdminCatalogsPage 2.2.0 Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>	2026-04-23 14:36:02 +02:00
Lars	377f365473	feat: Add TrainerContextsPage to navigation ... - Import TrainerContextsPage in App.jsx - Add route /trainer-contexts - Add 'Meine Bereiche' to main navigation (appNav.js) - Icon: Target (Zielscheibe) für Trainer-Bereiche - Visible in both desktop sidebar and mobile bottom nav version: 0.5.0 module: TrainerContextsPage 1.0.0 Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>	2026-04-23 14:26:10 +02:00
Lars	5e2820c63c	feat: Trainer-Kontext-System & Exercise Training Characters (v0.5.0) ... Migration 012: - exercise_training_characters (M:N junction table) - trainer_contexts (Fokussierte Trainer-Ansichten) - Indizes für Performance - Example seed data Backend (catalogs.py): - GET /api/trainer-contexts (list own contexts) - POST /api/trainer-contexts (create context) - PUT /api/trainer-contexts/{id} (update own context) - DELETE /api/trainer-contexts/{id} (delete own context) - Enriched responses mit focus_area_name, style_direction_name, training_type_name - Ownership-Validation (nur eigene Kontexte) Frontend: - TrainerContextsPage.jsx (vollständige CRUD-UI) - Kaskadierende Dropdowns (Fokusbereich → Stilrichtung) - is_style_independent Flag für stilunabhängige Kontexte - api.js erweitert (listTrainerContexts, create, update, delete) Architektur: - Flat Catalogs mit M:N überall - NULL = 'für alles geeignet' - Trainer-Kontexte für fokussierte Ansichten - Vorbereitung für 1000+ Übungen mit flexibler KI-Filterung version: 0.5.0 (backend + frontend) module: exercises 0.5.0, catalogs 1.5.0 page: TrainerContextsPage 1.0.0 Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>	2026-04-23 14:22:17 +02:00
Lars	9ab2bd31fa	fix: Update onClick handlers to use renamed functions ... - createTrainingStyle → createStyleDirection - updateTrainingStyle → updateStyleDirection - deleteTrainingStyle → deleteStyleDirection Fixes: Stilrichtungen tab showed blank screen due to undefined function calls version: 0.4.0 (frontend) module: AdminCatalogsPage 2.2.0 Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>	2026-04-23 12:57:23 +02:00
Lars	426efd4b83	fix: Frontend API Calls & Field Names für renamed tables ... - Updated api.js function names: - listTrainingStyles → listStyleDirections - createTrainingStyle → createStyleDirection - updateTrainingStyle → updateStyleDirection - deleteTrainingStyle → deleteStyleDirection - listTrainingStyleTargetGroups → listStyleDirectionTargetGroups - createTrainingStyleTargetGroup → createStyleDirectionTargetGroup - updateTrainingStyleTargetGroup → updateStyleDirectionTargetGroup - deleteTrainingStyleTargetGroup → deleteStyleDirectionTargetGroup - getTrainingStylesHierarchy → getStyleDirectionsHierarchy - Updated AdminCatalogsPage.jsx: - loadData() uses renamed API functions - CRUD functions renamed (createStyleDirection, etc.) - Matrix uses style_direction_id parameter - Hierarchy renders style_directions array - Fixes data binding between frontend and backend after table rename version: 0.4.0 (frontend) module: AdminCatalogsPage 2.2.0 Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>	2026-04-23 12:27:09 +02:00
Lars	a9a4c78a0e	feat: Admin-UI Trainingsstil-Dimension + Umbenennung ... Admin-UI Erweiterung: 1. Tab "Trainingsstile" → "Stilrichtungen" umbenannt - Überschrift: "Neue Stilrichtung" (statt Trainingsstil) - Tab-Label: "Stilrichtungen" 2. Neuer Tab "Trainingsstil" (Breitensport/Leistungssport) - CRUD-UI: Create/Update/Delete - Felder: Name, Kürzel (abbreviation), Beschreibung - State: trainingTypes, editingTT, newTT - Funktionen: createTrainingType, updateTrainingType, deleteTrainingType - Load-Logik: activeTab === 'training-types' Tab-Reihenfolge: - Fokusbereiche → Stilrichtungen → Trainingsstil → Hierarchie → Zielgruppen → Zuordnungen Pattern: Konsistent mit anderen Katalog-Tabs Version: AdminCatalogsPage 2.1.0	2026-04-23 12:17:31 +02:00
Lars	72c927e69e	feat: Backend API für training_types + Frontend api.js ... Backend (catalogs.py): - GET /api/training-types (Liste) - POST /api/training-types (Erstellen) - PUT /api/training-types/{id} (Bearbeiten) - DELETE /api/training-types/{id} (Löschen mit CASCADE-Check) - Cascade-Protection: Fehler wenn Übungen zugeordnet Frontend (api.js): - listTrainingTypes(filters) - createTrainingType(data) - updateTrainingType(id, data) - deleteTrainingType(id) - Export zum api-Objekt hinzugefügt Pattern: Konsistent mit anderen Katalog-Endpoints CRUD: Volle Admin-Verwaltung Version: 0.4.0	2026-04-23 12:12:48 +02:00
Lars	f243b236be	feat: Phase C - Admin-UI M:N Hierarchie & Matrix ... Frontend Admin-UI Refactoring (komplett): 1. Target Groups Tab überarbeitet (Global): - training_style_id Dropdown entfernt (Create + Edit) - Hierarchie-Anzeige entfernt (jetzt global unabhängig) - Nur noch Name, Beschreibung, Altersbereich 2. Neuer Tab 'Hierarchie' (Tree-View): - Fokusbereich → Trainingsstil → Zielgruppen - Expandable/Collapsible Nodes (▶/▼) - is_primary Kennzeichnung (★) - Hierarchische Darstellung mit Einrückung 3. Neuer Tab 'Zuordnungen' (M:N Matrix): - Checkbox-Matrix: Stile × Zielgruppen - Live-Toggle (Checkbox on/off) - Focus Area Kontext bei jedem Stil - is_primary Flag Anzeige (★) UX: - Tab-Reihenfolge: Fokusbereiche → Stile → Hierarchie → Zielgruppen → Zuordnungen - Responsive Tabelle mit Overflow-Scroll - Konsistente Card-basierte Layouts Version: 0.3.4 Page: AdminCatalogsPage 2.0.0	2026-04-23 10:55:35 +02:00
Lars	1891a4ab88	feat: Phase B - Frontend API für M:N Zielgruppen ... Frontend API Layer: - 5 neue api.js Funktionen für M:N Management - listTrainingStyleTargetGroups(filters) - Liste mit Filtern - createTrainingStyleTargetGroup(data) - Neue Zuordnung - updateTrainingStyleTargetGroup(id, data) - is_primary ändern - deleteTrainingStyleTargetGroup(id) - Zuordnung löschen - getTrainingStylesHierarchy() - Hierarchische Struktur für Tree-View Pattern: Konsistent mit bestehenden Catalog-Funktionen Export: Alle Funktionen zum api-Objekt hinzugefügt Version: 0.3.4 (Phase B)	2026-04-23 10:45:14 +02:00
Lars	1e5e18c0b3	feat: Migration 009 - Zielgruppen M:N Refactoring ... Backend Phase A (Database + API): - Migration 009: target_groups.training_style_id entfernt - Migration 009: Neue Junction-Tabelle training_style_target_groups - Migration 009: Datenmigration alte → neue Struktur (idempotent) - API: 5 neue Endpoints für M:N Management * GET /training-style-target-groups (mit Enrichment) * POST /training-style-target-groups (Upsert-Logik) * PUT /training-style-target-groups/{id} (is_primary) * DELETE /training-style-target-groups/{id} * GET /training-styles/hierarchy (für Tree-View) - API: GET/POST/PUT /target-groups jetzt global (ohne training_style_id) - API: DELETE /target-groups prüft beide Tabellen (CASCADE-Schutz) Architecture: - Eine Zielgruppe kann mehreren Stilen zugeordnet werden - Basis für Admin Tree-View + M:N Matrix UI Version: 0.3.4 Module: catalogs 1.3.0	2026-04-23 10:37:56 +02:00
Lars	2186bb3a69	fix: Admin-Navigation - Redirect /admin → /admin/catalogs ... Problem: Navigation-Link zeigte /admin, aber Route war /admin/catalogs Folge: Klick auf 'Admin' führte zu 404 (Catch-all Redirect zu /) Fix: Redirect-Route von /admin zu /admin/catalogs hinzugefügt version: 0.3.3	2026-04-23 09:00:28 +02:00
Lars	278d719e84	feat: Zielgruppen-Verwaltung (Target Groups CRUD + Admin UI) ... Backend: - GET /api/target-groups: Liste mit hierarchischem Kontext (focus_area → training_style → target_group) - POST /api/target-groups: Create (admin only) - PUT /api/target-groups/{id}: Update (admin only) - DELETE /api/target-groups/{id}: Delete (superadmin only) mit CASCADE-Schutz - Filter: by training_style_id, status Frontend: - api.js: listTargetGroups, createTargetGroup, updateTargetGroup, deleteTargetGroup - AdminCatalogsPage: Neuer Tab "Zielgruppen" (6. Tab) - Create-Form: training_style_id, name, description, min_age, max_age - List-View: Hierarchie-Anzeige (Fokusbereich → Stil → Zielgruppe + Altersbereich) - Inline-Editing mit Stil-Auswahl-Dropdown - Delete mit Confirmation Dialog Architektur: - Hierarchische Beziehung: target_groups.training_style_id → training_styles → focus_areas - CASCADE-Protection: DELETE verweigert wenn exercise_target_groups Einträge existieren - Backend liefert enriched data mit training_style_name + focus_area_name version: 0.3.2 modules: catalogs 1.2.0 pages: AdminCatalogsPage 1.1.0	2026-04-23 08:55:54 +02:00
Lars	d67f659e97	feat: Exercises-Router M:N Zuordnungen ... Backend API erweitert um M:N Katalog-Zuordnungen: - GET /exercises/{id}: Liefert focus_areas[], training_styles[], target_groups[], age_groups_catalog[] - POST /exercises: Akzeptiert focus_areas_multi[], training_styles_multi[], target_groups_multi[], age_groups_catalog[] - PUT /exercises/{id}: DELETE+INSERT Pattern für M:N Updates (konsistent mit skills) Rückwärtskompatibilität: - Legacy FK-Felder (focus_area_id, training_style_id, training_character_id) bleiben erhalten - Alte Aufrufe funktionieren unverändert - Neue M:N Felder sind optional version: 0.3.1 modules: exercises 0.4.0	2026-04-23 08:51:45 +02:00
Lars	63b1c09975	feat: Migration 008 - M:N Exercise Relations + Hierarchical Catalogs ... BREAKING CHANGE: Datenmodell-Umstellung von 1:1 auf M:N Beziehungen Migration 008: - Zielgruppen-Tabelle (target_groups) mit training_style_id Hierarchie - M:N Zuordnungstabellen: exercise_focus_areas, exercise_styles, exercise_target_groups - Altersgruppen-Dimension (exercise_age_groups) mit CHECK constraint - Hierarchische Struktur: training_styles.focus_area_id → focus_areas - Daten-Migration: Bestehende 1:1 Beziehungen zu M:N mit is_primary=true - Seed-Daten: Beispiel-Zielgruppen für Shotokan Architektur: - Smart Cascade-Logik (RESTRICT, Rerouting, Move) vorbereitet - Legacy-Spalten (focus_area_id, training_style_id) bleiben zur Rückwärtskompatibilität - Primary/Secondary Assignments via is_primary Flag Dokumentation: - .claude/docs/technical/DATABASE_SCHEMA.md (kontinuierlich gepflegt) - .claude/docs/functional/DOMAIN_MODEL.md (fachliche Anforderungen) - Migrations-Historie aktualisiert version: 0.3.0 (backend + frontend) modules: exercises 0.3.0, catalogs 1.1.0 DB_SCHEMA_VERSION: 20260423 Konzept: shinkan_anforderungsdokument_entwurf.md (§8.1, §8.3, §10.7)	2026-04-23 08:46:56 +02:00
Lars	0c7caea847	version: Bump to 0.2.0 + Changelog (Admin-Kataloge) ... CRITICAL FIX: Versions-Bump nachgeholt (war Pflicht laut ARCHITECTURE.md §2.5) Backend: - APP_VERSION: 0.1.0 → 0.2.0 - BUILD_DATE: 2026-04-21 → 2026-04-23 - DB_SCHEMA_VERSION: 20260421 → 20260422 (Migration 007) - MODULE_VERSIONS: catalogs 1.0.0 (neu), exercises 0.2.0 Frontend: - version.js neu erstellt - PAGE_VERSIONS: ExercisesPage 1.1.0, AdminCatalogsPage 1.0.0 Changelog: - Admin-Kataloge Feature komplett dokumentiert - Migration 007, Frontend-Integration, Formular-Standardisierung Deployment sollte jetzt korrekte Version zeigen + Katalog-Endpoints funktionieren.	2026-04-23 08:05:11 +02:00
Lars	c7cda03201	feat: Admin-managed exercise catalogs + frontend integration ... Backend (already committed): - Migration 007: focus_areas, training_styles, training_characters, skill_categories tables - routers/catalogs.py: 20 CRUD endpoints for all catalogs - routers/exercises.py: Updated to support new FK fields - Trainer focus area assignment for role-based filtering Frontend (new): - AdminCatalogsPage: Comprehensive admin UI with 5 tabs - Focus Areas (with color + icon) - Training Styles (hierarchical with parent_style_id) - Training Characters - Skill Categories (hierarchical) - Trainer Assignments (trainer → focus area mapping) - ExercisesPage: Updated to use catalog dropdowns - Focus area dropdown now loads from API - Added missing Training Style dropdown - Training character dropdown now loads from API - Uses IDs instead of hard-coded text values - App.jsx: Added /admin/catalogs route - api.js: Added all catalog endpoints All form fields standardized: labels on top, full width, left-aligned Ready for testing via /admin/catalogs	2026-04-23 07:52:03 +02:00
Lars	cbb783222c	refactor: Standardisiere Formular-Layout (Label oben, volle Breite, linksbündig) ... CSS (frontend/src/app.css): - .form-row: flex-direction column, volle Breite, margin-bottom 16px - .form-label: display block, font-weight 600, linksbündig - .form-input: width 100%, text-align left (statt right 90px), padding 10px 12px - textarea.form-input: resize vertical, min-height 80px - select.form-input: cursor pointer - .form-row--inline: Neue Variante für Ausnahmen (kurze Werte + Einheit) Dokumentation (.claude/rules/CODING_RULES.md): - Neue Regel Frontend §6: Formular-Standard (VERBINDLICH ab 2026-04-22) - Code-Beispiele für Standard-Layout (input, textarea, select) - Klare Regeln: Label = <label>, Pflichtfelder mit *, volle Breite, linksbündig - Inline-Variante nur für Ausnahmen (Zahlen mit Einheit) WICHTIG: Bestehende Formulare (Exercises, Clubs, Skills, TrainingPlanning) nutzen bereits größtenteils diese Struktur und profitieren automatisch von den CSS-Änderungen. Vorteile: - Konsistente UX über alle Formulare - Mobile-friendly (volle Breite, kein horizontal scrolling) - Bessere Lesbarkeit (Label als Überschrift) - Einfacher wartbar (ein Standard für alle) Nächster Schritt: Bestehende Formulare testen, ggf. kleine Anpassungen	2026-04-22 17:11:40 +02:00
Lars	7f156ba085	feat: Training Planning (core feature) complete ... Backend: - Created migration 006_training_planning.sql - training_units table (planned vs actual, status, notes) - training_unit_exercises M:N (order, duration, modifications) - Created routers/training_planning.py with full CRUD - List with filters (group, date range, status) - Get detail with exercises - Create/Update/Delete with access control - Quick create endpoint (auto-fills from group defaults) - Permission: trainer for own groups, admin for all - Registered training_planning router in main.py Frontend: - Complete TrainingPlanningPage with full planning workflow - Group selector + date range picker - List view with status badges (planned/completed/cancelled) - Create/Edit modal with exercise management - Drag to reorder exercises (▲▼) - Quick create button (one-click with group defaults) - Durchführung section (actual date/time, attendance, status) - Public notes + trainer-only notes - Updated api.js with deleteTrainingUnit and quickCreateTrainingUnit - Added /planning route to App.jsx - Navigation already configured (Calendar icon) This is the CORE feature - trainers can now plan and document training sessions. Next: Admin routes, role system refinement, testing	2026-04-22 16:54:34 +02:00
Lars	505a8e5e38	feat: Skills & Methods catalog complete ... Backend: - Created routers/skills.py with full CRUD - Skills: list (with category filter), get, create, update, delete - Methods: list (with category filter), get, create, update, delete - Default: only show active items - Read access: all authenticated users - Write access: admin only - Registered skills router in main.py Frontend: - Complete SkillsPage with 2 tabs (Fähigkeiten, Trainingsmethoden) - Browse by category with cards layout - Admin CRUD forms (importance rating for skills, duration/group size for methods) - Mobile-responsive grid layout - Updated api.js with all skill/method functions - Added /skills route to App.jsx Migration already exists: 003_catalogs.sql (skills, training_methods + seed data) Next: Training Planning (core feature)	2026-04-22 16:50:31 +02:00
Lars	8e027e02bb	feat: Clubs & Organization Management complete ... Backend: - Created routers/clubs.py with full CRUD - Clubs: list, get, create, update, delete (admin only) - Divisions: list, create, update, delete (admin only) - Training Groups: list, get, create, update, delete (admin/trainer) - Registered clubs router in main.py - Permission checks: admin for clubs/divisions, trainer for groups Frontend: - Complete ClubsPage with 3 tabs (Vereine, Sparten, Gruppen) - Role-based UI (admin sees all actions, trainer can manage groups) - Full CRUD forms with modals - Mobile-responsive card layouts - Updated api.js with all club/division/group functions Migration already exists: 002_organization.sql (clubs, divisions, training_groups) Next: Skills & Methods display (read-only)	2026-04-22 16:48:02 +02:00
Lars	8c7cf91cef	feat: Exercise CRUD complete ... Backend: - Registered exercises router in main.py - Migration 005 already created (exercises, exercise_skills, exercise_variants, exercise_media) - Full CRUD endpoints with visibility logic Frontend: - Complete ExercisesPage with list/create/edit/delete - Filter controls (focus_area, visibility, status) - Modal form with all fields - Skills multi-select - Mobile-responsive card layout Next: Clubs Management	2026-04-22 16:44:32 +02:00
Lars	de53ba3f66	fix: Add lucide-react dependency for navigation icons ... CRITICAL FIX: Build was failing because lucide-react was not in package.json - Added lucide-react ^0.344.0 to dependencies - Required for appNav.js and DesktopSidebar.jsx icon imports - Build should now succeed Apologies for missing this in initial design foundation commit!	2026-04-22 16:40:05 +02:00
Lars	46a90ae910	feat: Complete design foundation with responsive navigation ... Design System: - app.css already exists with full design tokens, dark mode, responsive breakpoints - CSS variables for colors, spacing, typography - Mobile-first layout with safe-area support (iOS notch) Navigation System: - config/appNav.js: Single source of truth for navigation items - Bottom-Nav for mobile (<1024px) with horizontal scrolling - DesktopSidebar for desktop (≥1024px) with fixed left sidebar - Role-based navigation (isAdmin adds Admin link) App.jsx Restructure: - Responsive layout: Bottom-Nav (mobile) + DesktopSidebar (desktop) - Protected/Public routes with loading states - Logout handler with confirmation PWA Setup: - viewport-fit=cover for notch support - apple-mobile-web-app meta tags - Icon links prepared (icons pending) Architecture: - Follows Mitai design patterns - Responsive breakpoint at 1024px - Single source of truth for navigation config Next: Icons, Exercise CRUD, Clubs/Groups Management	2026-04-22 16:25:36 +02:00
Lars	edb33b8fc3	fix: Use api.js in AuthContext for session persistence ... - AuthContext was using fetch() directly with relative URLs - Relative URLs went to nginx port (3098) instead of backend (8098) - Now uses api.getCurrentProfile() which has correct API_URL - Session persistence should work after browser refresh	2026-04-22 15:56:20 +02:00
Lars	c4b1b54f61	feat: Add navigation and basic pages structure	2026-04-22 06:48:18 +02:00
Lars	e4d052f182	fix: Add nginx SPA routing config	2026-04-21 16:30:11 +02:00
Lars	efc2a11a76	feat: Add Auth system with Login UI ... Backend: - Auth router (login, register, logout) - Profiles router (get current profile) - Registered in main.py Frontend: - LoginPage with login/register tabs - Dashboard with welcome screen - Simplified AuthContext for Shinkan - Protected routes in App.jsx - Public routes redirect when logged in Ready for testing! version: 0.1.0	2026-04-21 14:56:16 +02:00
Lars	b2bc8590c4	feat: Complete MVP setup - Docker, Frontend, Migrations, CI/CD ... Docker & Deployment: - docker-compose.yml (Prod: Port 3003/8003) - docker-compose.dev-env.yml (Dev: Port 3098/8098) - Backend Dockerfile (Python 3.12-slim) - Frontend Dockerfile (Node 20 + Nginx) - Gitea Actions (deploy-dev.yml, deploy-prod.yml) Frontend: - React 18 + Vite setup - package.json, vite.config.js, index.html - App.jsx (minimal with version display) - api.js (complete API client) - app.css + AuthContext from Mitai - main.jsx entry point Backend Migrations: - 001_auth_membership.sql (Auth + Features + Tier Limits) - 002_organization.sql (Clubs, Divisions, Training Groups) - 003_catalogs.sql (Skills + Methods with sample data) Documentation: - .claude/rules/ (ARCHITECTURE, CODING_RULES, etc.) - SHINKAN_PROJECT_SETUP.md (technical setup guide) Server: - Directories created on Pi: /home/lars/docker/shinkan[-dev] - Gitea Runner configured and running Ready for first deployment to dev.shinkan.jinkendo.de version: 0.1.0 date: 2026-04-21	2026-04-21 14:36:52 +02:00