Files

T

AgendaPro DevandClaude Opus 5 4c19244df9 feat: public landing page with magic login, brand palette and demo build flag

Adds a public funnel landing at `/` and moves the login to `/login`, rebuilt
around the panel's own colors instead of an invented palette.

Landing (`src/components/landing/`, one section per file, no props):
- Seven funnel sections composed by `LandingPage`. The hero's eight swatches are
  literally `PIE_COLORS` from `DashboardPage`, the same hex values the seed hands
  to avatars and services, so "your colors become your numbers" is literal.
- `BrandMark` becomes the single source for the logo, replicating
  `public/favicon.svg`. Blue is the action surface, orange only ever marks.
- `NotebookVisual` is the one deliberate exception to the palette: it is what the
  product replaces.
- Copy drops all system vocabulary; motion comes from `src/lib/motion.ts` with a
  single easing, and reduced-motion resolves `initial` to the final state so a
  never-firing `whileInView` cannot leave a section invisible forever.

Routing and bundle:
- `homePathFor` is the single definition of each role's destination.
- Landing, login, dashboard and calendar load lazily. Eager, the login dragged
  framer-motion (~40 KB gz) into every panel load and the landing downloaded
  recharts + FullCalendar (~187 KB gz) without charting anything. `clsx` is
  pinned to the `react` chunk because Rollup otherwise assigns it to `charts`,
  making the entry import 111 KB gz for a 200-byte utility.

Responsiveness (iPhone/iPad), verified with `npm run audit:responsive`:
- No touch form field below 16px, `dvh` height utilities, safe-area insets, and
  40px touch targets keyed off `pointer: coarse` rather than `sm:`.
- New `.ld-gutter`: `.safe-x` lives outside `@layer` and beats Tailwind's `px-*`,
  so it left the login's side padding at 0 on anything but an iPhone in
  landscape. No overflow check could see it — there was no overflow, just zero
  margin. The audit now guards it with a `gutter` check.
- `shell-height` no longer fires on pages that legitimately scroll; the static
  `raw-viewport-unit` scan covers those instead.

Production build:
- The Dockerfile now sets `VITE_DEMO_UI=1` as a build arg. `DEMO` is a build-time
  constant, so without it Vite eliminated the magic login and the "Ver como…"
  switcher: the deployed landing promised "no registration" and led to an empty
  form. Verified by building both ways and diffing the bundle.
- Service worker cache bumped to v2 so the orphaned pre-landing chunks get purged
  from returning visitors' caches.

Verified: typecheck clean; unit 39/39, e2e 33/33, admin 17/17, booking 12/12,
landing 13/13 (WebKit), PWA passed against the real production build.

Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>

2026-07-28 14:25:58 -06:00

2.0 KiB

Raw Permalink Blame History

Task 2 Implementation Report

Scope

Implemented only the production AgendaMax service worker and its production-only registration. Existing .superpowers/sdd/* changes and graphify-out/* outputs were preserved and were not staged.

Changed Files

public/sw.js: added versioned shell/static caching with agendamax-shell-v1, install/activate lifecycle handling, network-first navigation fallback, and cache-first handling limited to script, style, image, font, manifest, and worker requests.
src/main.tsx: registered /sw.js after the React root render only when import.meta.env.PROD and service workers are supported.

Verification

npm.cmd run typecheck: exit 0.

> [email protected] typecheck
> tsc -b --noEmit

npm.cmd run build: exit 0. Vite transformed 2463 modules and emitted the production bundle.
Test-Path -LiteralPath "dist/sw.js": True; Vite copied the public worker to the production output.
git diff --check: no whitespace errors. Git emitted only LF-to-CRLF normalization warnings for existing/changed working-tree files.

Self-Review

Cache name and shell URLs match the Task 2 contract exactly.
Activation removes older cache names and claims clients after activation.
Fetch handling rejects non-GET requests, cross-origin requests, and paths beginning with /api/ before any response interception.
Navigation requests use network-first behavior and fall back to the cached root document.
Static caching is allowlisted by request destination; there is no catch-all cache path.
Registration is deferred until load, uses { updateViaCache: "none" }, and registration failure is non-fatal.
Only public/sw.js and src/main.tsx are intended for the Task 2 commit.

Concerns

Validation is static/build-level only; browser service-worker runtime behavior is intentionally left to the later PWA end-to-end task.
git diff --check reports normal line-ending normalization warnings from the existing PowerShell/Git configuration, not whitespace errors.

2.0 KiB Raw Permalink Blame History