forked from DevFW-CICD/website-and-documentation

Stephan Lo 43cbd69c9c refactor(docs): migrate existing content to v1 legacy structure

- Move all existing docs content (concepts, project, solution) to /docs/v1/
- Add legacy banner component to warn users about archived documentation
- Create v1 index page with legacy notice and redirect guidance
- Implement automatic banner display for all v1 paths
- Preserve all original content for reference during migration

This enables incremental content migration while maintaining access to
original documentation.

2025-10-23 14:54:08 +02:00

1 KiB

Raw Blame History

why we have architectural documentation

TN: Robert, Patrick, Stefan, Stephan 25.2.25, 13-14h

referring Tickets / Links

charts

we need charts, because:

external stakeholders (especially architects) want to understand our product and component structure(*)
our team needs visualization in technical discussions(**)
we need to have discussions during creating the documentation

(*): marker: "jetzt hab' ich das erste mal so halbwegs verstanden was ihr da überhaupt macht" (**) marker: ????

typed of charts

schichtenmodell (frontend, middleware, backend)
bebauungsplan mit abhängigkeiten, domänen
kontext von außen
komponentendiagramm,

decisions

openbao is backend-system, wird über apis erreicht

further topics / new requirements

runbook (compare to openbao discussions)
persistenz der EDP konfiguartion (zb postgres)
OIDC vs. SSI

1 KiB Raw Blame History