Files
carmanagement/DESIGN_MIGRATION_REPORT.md
T
root c77d0a8e89
Build & Push / Build & Push Docker Image (push) Failing after 10m39s
Rename legacy storefront app and references to carplace
Replace storefront naming across source, tests, docs, config, and production scripts. Rename the legacy top-level app directory and Carplace component files, remove duplicate storefront startup scripts, and refresh the lockfile.
2026-07-04 18:10:08 -04:00

48 lines
3.2 KiB
Markdown

# RentalDriveGo Phase 16 Design Migration
## Outcome
The Phase 16 visual system has been applied at source level to the legacy application front ends in this archive:
- `homepage`: retained as the authoritative Phase 16 marketing implementation already present in the legacy archive.
- `admin`: migrated to the Phase 16 token palette and component treatment; navigation was rebuilt as a responsive, accessible application shell.
- `dashboard`: migrated to the same semantic surfaces, typography, borders, shadows, focus treatment, dark theme, and blue/orange action hierarchy.
- `carplace`: migrated to the same public-site surfaces, conversion treatment, cards, forms, dark theme, and brand naming.
- `api`: intentionally unchanged. A visual migration should not casually rewrite business logic because that is how weekends disappear.
## Design rules applied
- Blue is the operational primary color.
- Orange is reserved for conversion emphasis and focus visibility.
- Green is restored to success/status meaning instead of being used as a disguised primary action.
- Light and dark themes share semantic tokens rather than unrelated hard-coded palettes.
- English and French remain LTR; Arabic continues to use document RTL and an Arabic font fallback stack.
- Interactive controls use a minimum 44px target, visible focus treatment, reduced-motion handling, and high-contrast fallbacks.
- Cards and panels use the Phase 16 radius, border, surface, and shadow hierarchy.
- The retired `RentalDriveGo` name was replaced with `RentalDriveGo` throughout all frontend source files.
## Important source finding
The supplied `RentalDriveGo_Phase16_Evidence_Package_v1.0.zip` is an evidence and launch-governance package, not the Phase 16 source repository. It contains 98 files, while its manifest describes a separate 648-file repository that was not included. The legacy archive already contained most of that repository's marketing homepage implementation: 182 files match the Phase 16 manifest checksums exactly. That embedded homepage implementation was therefore used as the reliable visual source of truth rather than fabricating a new design from launch paperwork.
## Files added
- `admin/src/styles/phase16-tokens.css`
- `dashboard/src/styles/phase16-tokens.css`
- `carplace/src/styles/phase16-tokens.css`
- `scripts/validate-phase16-design.mjs`
- `DESIGN_MIGRATION_REPORT.md`
- `PHASE16_DESIGN_MIGRATION_MANIFEST.json`
## Validation performed
- Parsed 633 TypeScript and TSX source files with TypeScript 5.8 syntax validation: passed.
- Checked 53 CSS files for balanced rule blocks: passed.
- Verified all three migrated apps import the Phase 16 tokens: passed.
- Verified no retired `RentalDriveGo` branding remains in frontend source: passed.
- Ran `node scripts/validate-phase16-design.mjs`: passed.
## Validation not claimed
A full dependency-backed build and browser regression suite was not run. The supplied legacy archive omits its root workspace configuration and the local packages referenced as `@rentaldrivego/types` and `@rentaldrivego/database`. The Phase 16 evidence upload also omits the source repository and dependency lockfile it references. Those are packaging defects in the inputs, not facts to conceal with optimistic prose.