mocode-software/meldestelle
1
0
Fork 0
Code Issues Pull Requests 1 Actions Packages Projects Releases Wiki Activity
Files
2c8d16b27f75590afefe9b8f2beff5ca15b779dd
meldestelle/docs
T
History
stefan f82dbd64a5 Integrate Ktor HTTP clients and repositories for Veranstalter and Turnier features: 
- Add `ApiRoutes` for central backend routing configuration.
- Implement `DefaultVeranstalterRepository` and `DefaultTurnierRepository` with Ktor clients.
- Add domain models (`Turnier`, `Bewerb`, `Abteilung`, `Veranstalter`) and respective repository interfaces.
- Replace fake VeranstalterRepository with real implementation.
- Update DI with `veranstalterModule` and HTTP client injection.
- Simplify TokenProvider and update HttpClient setup (timeouts, retries, logging).
- Mark roadmap tasks B-2 as partially complete.
2026-04-03 01:09:35 +02:00
..
_archive
Migrate frontend navigation to V3: archive Navigation V2, implement updated screen-tree and back-stack rules, and adapt documentation for startable MVP flow.
2026-04-02 20:09:26 +02:00
01_Architecture
Update documentation for Navigation V3 and tenant concept: Mark Navigation V2 as deprecated, link replacement documentation, and expand tenant concept details with frontend and backend integration guidelines.
2026-04-02 23:17:07 +02:00
02_Guides
Migrate frontend navigation to V3: archive Navigation V2, implement updated screen-tree and back-stack rules, and adapt documentation for startable MVP flow.
2026-04-02 20:09:26 +02:00
03_Domain
Migrate frontend navigation to V3: archive Navigation V2, implement updated screen-tree and back-stack rules, and adapt documentation for startable MVP flow.
2026-04-02 20:09:26 +02:00
04_Agents
Integrate Ktor HTTP clients and repositories for Veranstalter and Turnier features:
2026-04-03 01:09:35 +02:00
05_Backend
Remove deprecated isAuthenticated logic from PingViewModel and related UI components
2026-03-17 00:18:02 +01:00
06_Frontend
Mark sprint tasks A-1 and parts of B-1 through B-3 as complete. Finalize design inventory, add Editier-Formulare guidelines, Bewerb creation workflow with Abteilungs-Logik, and Veranstaltungs-Kassa wireframes to documentation.
2026-04-03 00:39:59 +02:00
07_Infrastructure
chore: archive outdated architecture and roadmap documents, normalize documentation structure and metadata
2026-03-15 20:00:51 +01:00
90_Reports
docs(reports): add comprehensive status and recommendation reports for key roles
2026-04-02 11:15:38 +02:00
99_Journal
Migrate frontend navigation to V3: archive Navigation V2, implement updated screen-tree and back-stack rules, and adapt documentation for startable MVP flow.
2026-04-02 20:09:26 +02:00
BilderSuDo
docs: add UI screenshots for SuDo documentation
2026-01-26 14:35:26 +01:00
Bin
chore: archive outdated architecture and roadmap documents, normalize documentation structure and metadata
2026-03-15 20:00:51 +01:00
Neumarkt2026
feat(horses-service): remove legacy configuration and repository classes
2026-03-23 13:47:04 +01:00
OePS
Add documentation and templates for Start-/Ergebnislisten v07: Introduce foundational templates, print styles and partials, and consolidate related session notes.
2026-03-30 22:55:51 +02:00
ScreenShots
feat(pferde-feature): introduce Pferde management module with screens, ViewModel, and domain models
2026-03-31 12:20:03 +02:00
temp
Finalize domain model: define event → tournament → class → division hierarchy, multi-tournament account structures, and event-wide cashbox aggregation logic. Add division types and update glossary tasks.
2026-04-02 17:53:49 +02:00
README.md
docs: update README with Zora architecture and roadmap links, add .keep file
2026-03-05 11:34:40 +01:00

README.md

📚 Projektdokumentation "Meldestelle"

Willkommen im "Gehirn" des Projekts. Dieses Verzeichnis ist die Single Source of Truth.

📂 Struktur

🏗️ Core

🛠️ Tech Stack

🤖 Process

📝 Regeln für die Dokumentation

  1. Docs-as-Code: Doku liegt beim Code und wird im selben PR aktualisiert.
  2. Frontmatter: Jede Markdown-Datei muss einen YAML-Header haben: 
    ---
type: [ADR, Guide, Reference, Report, Journal]
status: [DRAFT, ACTIVE, DEPRECATED, ARCHIVED]
owner: [Rolle]
---
  3. Archivierung: Lösche nichts. Verschiebe veraltetes Wissen in _archive Ordner oder markiere es als ARCHIVED.

🚀 Quick Links

Reference in New Issue View Git Blame Copy Permalink