19-05-2026 Rebrand Pressekonto, Hub-Flux UI und Legacy-Media-Migration

Umbenennung presseportale → pressekonto in Domains, Themes und Dokumentation.
Design-Tokens, Portal-Shell, Customer-Dashboard, Auth- und Admin-PM-Views.
Artisan-Befehl migrate:legacy-media mit Tests und Hub-Flux-Entwicklungsdocs.

Co-authored-by: Cursor <cursoragent@cursor.com>
This commit is contained in:
Kevin Adametz 2026-05-19 16:36:13 +00:00
parent 092ee0e918
commit 0a3e52d603
112 changed files with 8464 additions and 1649 deletions

View file

@ -65,7 +65,7 @@ Du benötigst **mindestens 2 Vite-Ports**:
│ └──────────────────┘ └──────────────────┘ │
│ ↓ ↓ │
│ ┌──────────────────┐ ┌──────────────────┐ │
│ │ presseportale.test │ │ presseecho.test │ │
│ │ pressekonto.test │ │ presseecho.test │ │
│ │ │ │ businessp24.test│ │
│ └──────────────────┘ └──────────────────┘ │
│ │
@ -80,14 +80,14 @@ Du benötigst **mindestens 2 Vite-Ports**:
- Port: **5177**
- Input: `resources/css/portal.css`
- Build: `public/build/portal`
- HMR: `assets.presseportale.test`
- HMR: `assets.pressekonto.test`
- FluxUI: ✅ Ja
#### ✅ `vite.web.config.js`
- Port: **5178** (geändert von 5177!)
- Input: `theme-presseecho.css`, `theme-businessportal24.css`
- Build: `public/build/web`
- HMR: `assets-web.presseportale.test`
- HMR: `assets-web.pressekonto.test`
- FluxUI: ❌ Nein
#### ❌ `vite.config.js` (deprecated)
@ -190,14 +190,14 @@ npm run build:web
| URL | Vite-Port | Theme | FluxUI |
|-----|-----------|-------|--------|
| https://presseportale.test | 5177 | portal | ✅ |
| https://pressekonto.test | 5177 | portal | ✅ |
| https://presseecho.test | 5178 | presseecho | ❌ |
| https://businessportal24.test | 5178 | businessportal24 | ❌ |
## HMR (Hot Module Replacement)
- **Portal:** `wss://assets.presseportale.test` → Port 5177
- **Web:** `wss://assets-web.presseportale.test` → Port 5178
- **Portal:** `wss://assets.pressekonto.test` → Port 5177
- **Web:** `wss://assets-web.pressekonto.test` → Port 5178
⚠️ **Wichtig:** Traefik muss beide HMR-Hosts routen!
@ -210,12 +210,12 @@ Stelle sicher, dass Traefik beide Vite-Ports routet:
# docker-compose.yml oder traefik.yml
labels:
# Portal Assets
- "traefik.http.routers.vite-portal.rule=Host(`assets.presseportale.test`)"
- "traefik.http.routers.vite-portal.rule=Host(`assets.pressekonto.test`)"
- "traefik.http.routers.vite-portal.service=vite-portal"
- "traefik.http.services.vite-portal.loadbalancer.server.port=5177"
# Web Assets
- "traefik.http.routers.vite-web.rule=Host(`assets-web.presseportale.test`)"
- "traefik.http.routers.vite-web.rule=Host(`assets-web.pressekonto.test`)"
- "traefik.http.routers.vite-web.service=vite-web"
- "traefik.http.services.vite-web.loadbalancer.server.port=5178"
```
@ -223,11 +223,11 @@ labels:
### 2. DNS/Hosts-Datei aktualisieren
```
127.0.0.1 presseportale.test
127.0.0.1 pressekonto.test
127.0.0.1 presseecho.test
127.0.0.1 businessportal24.test
127.0.0.1 assets.presseportale.test
127.0.0.1 assets-web.presseportale.test
127.0.0.1 assets.pressekonto.test
127.0.0.1 assets-web.pressekonto.test
```
### 3. Blade-Templates aktualisieren
@ -258,7 +258,7 @@ Diese Dateien werden nicht mehr benötigt:
npm run dev:all
# 2. Browser öffnen
# - https://presseportale.test (Backend)
# - https://pressekonto.test (Backend)
# - https://presseecho.test (Frontend Grün)
# - https://businessportal24.test (Frontend Rot)