mocode-software/meldestelle
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
c11bffef22
meldestelle/docs
History
Stefan Mogeritsch c11bffef22 feat(docs+domain): refine event and tournament models, align with updated domain terminology 
- **Documentation:**
  - Added `2026-04-09_Session_Log_Turnier_Veranstaltung_Domain_Alignment.md` to document validation and updates to `Veranstaltung` and `Turnier` domain models.
  - Updated `Overview.md` to reflect new terminology and added attributes for `Veranstaltung` (`Austragungsplätze`, `Artikel-Preisliste`) and `Turnier`
(`Turnierbeauftragter`, updated `Reglement`, `Nennschluss`, `Nachnenngebühr`, and `Nenntauschbörse`).

- **Domain Updates:**
  - Adjusted `Turnier` model: renamed `richterObmannId` → `turnierbeauftragterId`, added missing fields (`nennschluss`,
2026-04-09 10:09:21 +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 Remove Dom prefix from domain models: rename classes to reflect business terminology, update references in tests, repositories, and services; add ADR for new naming conventions. 2026-04-08 23:00:52 +02:00
02_Guides Update setup guide and README to emphasize desktop-first development. Add detailed instructions for local setup, including prerequisites (JDK 25, Gradle 9.4.0, Docker), and clarify Docker backend stack as optional. Mark Sprint C tasks C-1 and C-2 as complete. 2026-04-03 23:11:20 +02:00
03_Domain feat(docs+domain): refine event and tournament models, align with updated domain terminology 2026-04-09 10:09:21 +02:00
04_Agents Create C-3 proposal for reorganizing docs/ folder structure: document hotspots, define target hierarchy, and outline migration plan. Update README.md and Curator roadmap with proposal details. 2026-04-03 23:19:28 +02:00
05_Backend Document tenant-aware database schema, multi-tenant strategy, and API references: 2026-04-03 22:59:45 +02:00
06_Frontend Update MVVM + UDF documentation: add metadata, extend examples, and consolidate references. Mark Curator roadmap tasks as complete. 2026-04-03 23:05:17 +02:00
07_Infrastructure Remove deprecated ZnsLegacyParsersTest.kt, synchronize database schema with Exposed domain models (migration V010), add license-related fields to Reiter, integrate updated LicenseMatrixService fallback logic, improve ZnsImportService with file archiving, and add ZNS testing runbook. 2026-04-06 01:46:26 +02:00
90_Reports docs(reports): add comprehensive status and recommendation reports for key roles 2026-04-02 11:15:38 +02:00
99_Journal feat(docs+domain): refine event and tournament models, align with updated domain terminology 2026-04-09 10:09:21 +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 feat(docs+domain): refine event and tournament models, align with updated domain terminology 2026-04-09 10:09:21 +02:00
README.md Create C-3 proposal for reorganizing docs/ folder structure: document hotspots, define target hierarchy, and outline migration plan. Update README.md and Curator roadmap with proposal details. 2026-04-03 23:19:28 +02: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

📦 Hinweis zur Reorganisation (C-3)

Im Rahmen von C-3 wird eine Konsolidierung von Medien/Binärartefakten unter docs/80_Assets/ sowie eine feinere Gliederung von Reports/Journals vorgeschlagen. Aktuell finden keine Verschiebungen statt – Details siehe Proposal oben.