Add 12 ADRs documenting frontend architecture decisions

2026-04-26 16:34:34 +02:00
parent c575992d64
commit 8f2632f456
13 changed files with 302 additions and 0 deletions
@@ -0,0 +1,21 @@
+# ADR 0001: Migration from Next.js/React to Angular
+
+**Date:** 2026-04-26
+**Status:** Accepted
+
+## Context
+
+The project was initially built with Next.js (React). The development team already maintained an existing Angular stack for other projects. Running two separate frontend frameworks in parallel created an unnecessary knowledge split and increased maintenance overhead.
+
+Server-side rendering, which is Next.js's main differentiator, was not required for this application — all data is user-specific and served via authenticated API calls, making SSR provide little to no benefit.
+
+## Decision
+
+Migrate the frontend to Angular, reusing the existing Angular expertise and toolchain. The Next.js/React code (pages, components, utilities, middleware) is abandoned entirely.
+
+## Consequences
+
+- **Positive:** Single frontend framework across projects. Reuse of existing Angular expertise, libraries, and patterns.
+- **Positive:** No SSR complexity. The app is a pure SPA, which fits Angular's model.
+- **Negative:** Complete rewrite of frontend code. No incremental migration path between React and Angular.
+- **Residual:** Next.js artifacts (`.next/`, `next.config.js`, `src/modules/`, `src/middleware.ts`, etc.) were removed as part of the cleanup after the migration.