mocode-software/meldestelle
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
54f91c7309
meldestelle/docs/06_Frontend
History
StefanMoCoAt a3007b01ee
Some checks are pending
Desktop CI — Headless Tests & Build / Compose Desktop — Tests (headless) & Build (push) Waiting to run
Details
Add archived screenshots documentation and migrate new assets to docs/80_Assets/. Include system mockups, tournament files, and dashboard visuals for Neumarkt 2026.
2026-04-09 22:10:55 +02:00
..
Diagrams docs(frontend): add navigation and flow diagrams for wizard steps 2026-04-09 15:52:44 +02:00
E_Nennen Remove obsolete chat logs and migrate relevant assets from docs/Neumarkt2026/ and docs/BilderSuDo/ to docs/80_Assets/. Update references and initiate consolidation of documentation. 2026-04-09 22:02:14 +02:00
FIGMA Remove obsolete chat logs and migrate relevant assets from docs/Neumarkt2026/ and docs/BilderSuDo/ to docs/80_Assets/. Update references and initiate consolidation of documentation. 2026-04-09 22:02:14 +02:00
G_ErgebnisMaske Remove obsolete chat logs and migrate relevant assets from docs/Neumarkt2026/ and docs/BilderSuDo/ to docs/80_Assets/. Update references and initiate consolidation of documentation. 2026-04-09 22:02:14 +02:00
Guidelines feat(docs): finalize editing forms guideline and define empty state specification 2026-04-03 11:54:44 +02:00
Logs infra: clean up Keycloak configuration, enforce consistency in .env, and improve health checks 2026-03-06 11:23:24 +01:00
Reports 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
Screenshots Add archived screenshots documentation and migrate new assets to docs/80_Assets/. Include system mockups, tournament files, and dashboard visuals for Neumarkt 2026. 2026-04-09 22:10:55 +02:00
StartErgListen Remove obsolete chat logs and migrate relevant assets from docs/Neumarkt2026/ and docs/BilderSuDo/ to docs/80_Assets/. Update references and initiate consolidation of documentation. 2026-04-09 22:02:14 +02:00
Wireframes 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
ARCHITECTURE_RULES.md chore: remove obsolete screens from meldestelle-desktop module 2026-03-26 15:09:44 +01:00
feature-implementation-guide.md refactor(ping-feature): integrate DI refactor, enhance web build, and update feature workflow 2026-01-17 12:05:34 +01:00
Inventar_Frontend_Katalog.md docs(frontend): add navigation and flow diagrams for wizard steps 2026-04-09 15:52:44 +02:00
MVVM_UDF_Pattern.md 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
Navigation_Routing_Diagramm.md 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
Navigation_V2_Screen-Baum_und_Back-Stack.md 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
Navigation_V3_Screen-Baum_und_Back-Stack.md 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
offline-first-architecture.md chore: archive outdated architecture and roadmap documents, normalize documentation structure and metadata 2026-03-15 20:00:51 +01:00
README.md 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
screen-flow_1-04-26.md feat(management-feature): add centralized administration screens and back-navigation support 2026-04-01 17:26:44 +02:00
state-management-strategy.md docs: add state-management strategy reference and SQLDelight session log 2026-01-28 13:00:55 +01:00
Teststrategie_Desktop.md Mark A-1 as complete: Add detailed QA Test-Strategie for Compose Desktop App, including test pyramid, tooling, conventions, and CI/CD integration; link roadmap and strategy documents. 2026-04-02 18:46:40 +02:00
web-setup.md chore: archive outdated architecture and roadmap documents, normalize documentation structure and metadata 2026-03-15 20:00:51 +01:00

README.md

type status owner last_update
Reference ACTIVE Frontend Expert 2026-04-03

Frontend-Architektur "Meldestelle Portal"

Dieses Verzeichnis dokumentiert die Architektur und die technischen Details des KMP-Frontends "Meldestelle Portal".

Übersicht

Das Frontend ist eine Kotlin Multiplatform (KMP)-Anwendung, die für die folgenden Ziele entwickelt wird:

  • Desktop (JVM): Eine eigenständige Desktop-Anwendung.
  • Web (JS/Wasm): Eine moderne Web-Anwendung, die im Browser läuft.

Die Architektur ist auf Offline-Fähigkeit und eine reaktive UI ausgelegt.

Modul-Struktur

Das frontend-Verzeichnis ist wie folgt strukturiert, um eine klare Trennung der Verantwortlichkeiten zu gewährleisten:

  • shells/: Die ausführbaren Anwendungen (Assembler-Module), die die App für eine bestimmte Plattform (Desktop, Web) zusammenbauen.
  • features/: Vertikale Slices der Anwendung. Jedes Feature-Modul kapselt eine bestimmte Funktionalität (z.B. auth-feature, ping-feature). Wichtig: Ein Feature-Modul darf niemals von einem anderen Feature-Modul abhängen.
  • core/: Gemeinsame Basis-Module, die von allen Features genutzt werden. Dazu gehören:
    • design-system/: Compose-Komponenten, Themes, Farben.
    • domain/: Fachliche Kernlogik und Datenmodelle des Frontends.
    • local-db/: SQLDelight-Datenbank-Setup und Queries.
    • navigation/: Navigations-Logik und Routen-Definitionen.
    • network/: Ktor-Client und API-Definitionen.

Kerntechnologien

  • UI: Compose Multiplatform für eine deklarative, plattformübergreifende UI.
  • Persistenz (Offline-First): SQLDelight für die lokale Speicherung von Daten.
  • State Management: Kotlin Coroutines und Flow in Kombination mit ViewModels.
  • Dependency Injection: Koin für die lose Kopplung von Komponenten.
  • Netzwerk: Ktor Client für die Kommunikation mit dem Backend.

Wichtige Dokumente