jobtrackingapp/docs/launch-site/HOMEPAGE_AUDIT.md

LAUNCH-00 source audit - partial checkpoint

Design pattern and asset inputs

• Linear shows the workspace near the top and lets specific workflow examples explain the product. The Premium concept explores a genuine Jobjakt dashboard in a similar position using its own visual treatment. Linear homepage
• Notion groups its feature presentation around recognizable actions. All four Jobjakt concepts use three short outcomes tied to tracking, Career Profile and CV preparation. Notion product overview
• Basecamp combines a direct product explanation with a distinct tour action. The Jobjakt hero prototypes separate a proposed registration action from the feature walkthrough. Basecamp homepage

The four rendered concepts use verified synthetic product captures and one original illustration. Signup submission, degraded auth, baseline performance and native accessibility remain open in LAUNCH-00. A live commercial claim or current price still needs independent evidence and approval.

Rendered baseline reconciliation, 10 November 2026

The separately published A3 evidence at bd34a3504f7e849c41b48db444f0e1f16324a16f includes docs/ui-modernisation/visual-correction/LANDING_BASELINE_REVIEW.md and evidence/landing-baseline/BROWSER.json under the same directory. The runtime was e8e7d83958587e8b5a4b93d03d3e736896df5a48. This closes the rendered anonymous navigation and raw export observations at that baseline.

12 fixture journeys covered 320, 768 and 1440 px in EN/NB and both themes. Keyboard feature navigation, local language selection and entry into existing sign-in and registration routes passed. No registration was submitted. All three preview SVGs loaded. All 12 states reported missing landmark best practices, and the raw static response lacked a hero heading, canonical and locale alternates. The anonymous language switch attempted 24 authenticated preference writes that the fixture rejected. Public language changes should use the existing local choice until the user has a session. The dashboard SVG email was anonymised in the capture fixture only.

The captured images are browser evidence of the existing homepage. The preview SVGs inside it are still illustrations. For LAUNCH-01, source potential real product captures from the published A3 evidence viewer, including dashboard, applications-selection, career and the existing CV editor captures. Before using an image, inspect the pixels and bind it to its actual route, source commit, language, viewport, fixture and asset rights. The A3 development branch has outstanding visual acceptance. Its captures are candidates for review mockups. Market, provider and pricing claims require the separate claim review.

Open audit inputs include contemporary design pattern research, asset rights, realistic registration and degraded-auth behaviour, measured performance and native review. The four LAUNCH-01 concepts remain to be rendered.

2026-11-02. feature/launch-site-redesign, accepted conditional baseline 5cb903b989742b7a96cb22ddf4c0e24993b18980. Full authoritative homepage prompt read. LAUNCH-00 IN_PROGRESS; LAUNCH-01 concepts NOT YET PRODUCED. No final design selected or implemented.

Finding	Source evidence	User implication / proposed direction
Main Get started opens sign-in	LandingPage.tsx passes goToLogin to hero CTA; Free-plan CTA separately goes to /register	Registration intent has an extra mode-selection step. Propose direct registration while preserving sign-in return state
Existing signup owner should be reused	App.tsx:522 maps /register to LoginPage initialMode=register; LoginPage respects auth config and registration availability	No second onboarding implementation; final CTA must reflect actual enabled registration
Product previews are conceptual assets	LandingPage.tsx uses /mockups/dashboard.svg, pipeline.svg, workspace.svg	Replace with provenance-bound synthetic captures in approved design; never label current artwork a genuine screenshot
Implementation details occupy hero copy	LandingPage renders React/TypeScript/ASP.NET/EF/FastAPI/Gmail text	Replace with plain user outcomes across professions; framework names do not explain job-search value
Marketing content depends on client execution and auth probe	app/page.tsx loads ClientShell; ClientShell.tsx uses ssr:false; LandingPage shows loading until /auth/me resolves/rejects	Crawlable HTML and loading/failure behavior need measured review; cannot assume static export includes full marketing copy
Metadata is generic	app/layout.tsx has global title/description and initial lang=en	Design market/content-locale metadata and canonical/alternate rules without disturbing authenticated routing; no SEO score claimed
Brand continuity exists	Indigo/cyan hero, shared MUI/theme, custom en/nb translations	Explore distinct compositions while preserving identity; avoid rebuilding app shell
Product presentation is limited	Six feature cards, six steps and three conceptual images; no actual redesigned CV/import/gallery imagery	Prioritise actual accepted tracking, canonical Career Profile and reviewed document workflow; do not imply new Global Jobs is shipped
Pricing shows capabilities, not amounts	planCatalog.ts defines Free/Pro, explicitly delegates commercial terms to configured checkout	Do not invent amounts/currencies/trials or promise active Pro AI; release and entitlement validation required
Footer lacks privacy/legal links in this component	LandingPage footer contains copyright text and sign-in button	Verify existing legal destinations and approved copy before adding links; no invented compliance claims
Responsive layouts are declared	MUI breakpoints change hero controls, feature grids, plan columns and footer	Source intent only; mobile/tablet/keyboard/reflow/contrast require actual rendered checks

Preserve signed-in redirect to /dashboard, interrupted protected-route return state, shared language behavior, plan policy ownership and existing registration constraints. New public market language must not overwrite job-ad or document output language. Existing custom en/nb implementation is not full European locale support.

Not yet checked: current rendered desktop/mobile site, external design-pattern research, runtime signup, slow/offline auth probe, keyboard/AT/contrast, image loading/performance, crawled output, real deployment availability and final asset rights. These omissions keep LAUNCH-00 open. No product tests were rerun for this Markdown-only source checkpoint.