feat(design): v2 opt-in (atmospheric dusks) — Settings toggle, cookie-mirrored

Lets users opt into the new atmospheric design without affecting users on v1. Adds a beta-flag toggle in Settings → Design. Server-side preference persists across devices; a cookie mirrors it so unauthenticated Twig pages do correct first-paint without an extra DB roundtrip. Backend: - User.designVersion column (nullable VARCHAR(10); null defaults to 'v1') - Migration Version20260515120000 - PATCH /api/user/design endpoint accepting 'v1'|'v2', sets wevisto_design cookie - SpaController injects data-design on <html> + refreshes the cookie on every SPA load (keeps cross-device pref in sync) - Twig templates (base, login, register, help, setup, token-*) read the cookie via {{ app.request.cookies.get('wevisto_design')|default('v1') }} so login/setup pages also respect the user's design choice Frontend: - design-v2.scss — opt-in overlay scoped under [data-design="v2"]. Overrides --color-* tokens to dusk variants per theme (warm-craft → amber, ocean-dusk stays, etc.), adds harbor photo backdrop via body::before with theme tint via body::after. Glass-card blur on existing surfaces. v1 untouched. - harbor.jpg shipped as a public asset (270KB, single-fetch, cached) - User type gains designVersion ('v1' | 'v2') - SettingsView toggle (Original / Atmospheric) calls the API, updates the data-design attribute optimistically, reverts on failure Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-15 12:28:44 -04:00
parent 5bb8289a54
commit a302ac09b4
36 changed files with 367 additions and 58 deletions
@@ -0,0 +1,28 @@
+<?php
+
+declare(strict_types=1);
+
+namespace DoctrineMigrations;
+
+use Doctrine\DBAL\Schema\Schema;
+use Doctrine\Migrations\AbstractMigration;
+
+final class Version20260515120000 extends AbstractMigration
+{
+    public function getDescription(): string
+    {
+        return 'Add user.design_version — opt-in flag for the v2 (dusks) redesign; null defaults to v1';
+    }
+
+    public function up(Schema $schema): void
+    {
+        // Nullable on purpose: null means the user has never touched the preference,
+        // which the app treats as v1. New explicit values are 'v1' or 'v2'.
+        $this->addSql('ALTER TABLE "user" ADD design_version VARCHAR(10) DEFAULT NULL');
+    }
+
+    public function down(Schema $schema): void
+    {
+        $this->addSql('ALTER TABLE "user" DROP COLUMN design_version');
+    }
+}