tegwick
00469c4cc0
Replace vergabe's blue brand-* palette with whynot's near-black/paper/yellow visual language. Tokens vendored at static/src/vendor/whynot-design/ (synced from commit 9419f16 via scripts/sync-whynot-design.sh / make sync-whynot-design). main.css imports the vendored CSS first, exposes ink/paper/hi as Tailwind @theme tokens (bg-paper, text-ink, border-line, etc.), and re-tones every component class (.btn-*, .card, .field-row, .phase-*, .form-input, .table-*, .sidebar-*). Border radii drop to whynot's 0-4px; .card loses its shadow. Legacy text-brand-* / bg-brand-* / border-brand-* template references are kept working via @theme aliases that map the old blue scale onto the whynot ink ramp — Phase 1 is tokens-only, no template churn. btn-danger keeps an off-spec red (#B22222) as a local --danger var until upstream defines a canonical destructive color. base.html body class swapped: bg-slate-50 → bg-paper-2 text-ink. Phase 2 (component adoption) deferred until whynot-design ships Lit web components + missing atoms (Card, Modal, Input, Table, Toast). See wiki/DesignSystem.md and history/2026-05-23-whynot-design-cross-framework-analysis.md. Verified: 8/8 e2e tests pass; dev server boots; static/dist/main.css contains no #3b5bdb references. Visual pixel-level verification still pending Bernd's browser walk. |
||
|---|---|---|
| .. | ||
| README.md | ||
| WP-0001-projektgeruest.md | ||
| WP-0002-fachmodelle.md | ||
| WP-0003-basis-ui.md | ||
| WP-0004-dashboard-ausschreibungen.md | ||
| WP-0005-lose-anforderungen.md | ||
| WP-0006-aufgaben-bieterfragen.md | ||
| WP-0007-dokumente.md | ||
| WP-0008-preise.md | ||
| WP-0009-abgabe-nachbetrachtung.md | ||
| WP-0010-partner-bibliothek.md | ||
| WP-0011-marktbegleiter.md | ||
| WP-0012-querschnitt.md | ||
| WP-0013-feedback-bugs.md | ||
| WP-0014-aufgaben-lose-scores.md | ||
| WP-0015-aufgaben-verknuepfungen-frist-issuefacade.md | ||
| WP-0016-issue-facade-integration.md | ||
| WP-0017-whynot-design-tokens.md | ||
Workplans — Vergabe Teilnahme
Vollständiger Implementierungsplan in 12 Ralph-Loop-Workplans.
Jeder Workplan ist mit /ralph-workplan workplans/WP-XXXX-slug.md zu starten.
Reihenfolge
| Workplan | Inhalt | Tasks | Abhängigkeit |
|---|---|---|---|
| WP-0001 | Projektgerüst (Django, uv, Tailwind, Docker) | 12 | — |
| WP-0002 | Alle Fachmodelle, Migrationen, Admin, Seed | 14 | WP-0001 |
| WP-0003 | Basis-UI: Shell, Templates, Template-Tags, Nav | 10 | WP-0002 |
| WP-0004 | Dashboard, Ausschreibungen CRUD | 12 | WP-0003 |
| WP-0005 | Lose und Anforderungen | 8 | WP-0004 |
| WP-0006 | Aufgaben und Bieterfragen | 6 | WP-0005 |
| WP-0007 | Dokumentenmanagement | 6 | WP-0006 |
| WP-0008 | Preise und Marktpreisauswertung | 5 | WP-0007 |
| WP-0009 | Abgabe und Nachbetrachtung | 5 | WP-0008 |
| WP-0010 | Subunternehmer, Partner, Bibliothek | 7 | WP-0009 |
| WP-0011 | Marktbegleiter-Analyse | 4 | WP-0010 |
| WP-0012 | Freigaben, Flexible Felder, Feedback, E2E-Tests | 8 | WP-0011 |
Start
# Neue Session starten (Kontext muss frisch sein — /compact bei Bedarf)
/ralph-workplan workplans/WP-0001-projektgeruest.md --max-iterations 15
Referenzdokumente
wiki/ProductRequirementsDocument.md— fachliche Anforderungenwiki/ArchitectureBlueprint.md— technische Architektur, Modelle, URL-Strukturwiki/UseCaseCatalog.md— 56 Use Cases mit konkreten UI-Abläufen