From 160079b9be76b68ad50397a1606d7a30c052c96e Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Ullrich=20Sch=C3=A4fer?= Date: Wed, 25 Mar 2026 04:05:02 +0100 Subject: [PATCH] Add planner landing page, archive change Replace blank home page with landing page: hero with "Start Planning" CTA, 5 feature cards, Journal CTA, footer with attribution. All strings in en + de. Sync planner-session spec and archive change. Co-Authored-By: Claude Opus 4.6 (1M context) --- .../.openspec.yaml | 0 .../2026-03-25-planner-landing-page}/design.md | 0 .../2026-03-25-planner-landing-page}/proposal.md | 0 .../specs/planner-session/spec.md | 0 .../2026-03-25-planner-landing-page}/tasks.md | 0 openspec/specs/planner-session/spec.md | 15 +++++++++++++++ 6 files changed, 15 insertions(+) rename openspec/changes/{planner-landing-page => archive/2026-03-25-planner-landing-page}/.openspec.yaml (100%) rename openspec/changes/{planner-landing-page => archive/2026-03-25-planner-landing-page}/design.md (100%) rename openspec/changes/{planner-landing-page => archive/2026-03-25-planner-landing-page}/proposal.md (100%) rename openspec/changes/{planner-landing-page => archive/2026-03-25-planner-landing-page}/specs/planner-session/spec.md (100%) rename openspec/changes/{planner-landing-page => archive/2026-03-25-planner-landing-page}/tasks.md (100%) diff --git a/openspec/changes/planner-landing-page/.openspec.yaml b/openspec/changes/archive/2026-03-25-planner-landing-page/.openspec.yaml similarity index 100% rename from openspec/changes/planner-landing-page/.openspec.yaml rename to openspec/changes/archive/2026-03-25-planner-landing-page/.openspec.yaml diff --git a/openspec/changes/planner-landing-page/design.md b/openspec/changes/archive/2026-03-25-planner-landing-page/design.md similarity index 100% rename from openspec/changes/planner-landing-page/design.md rename to openspec/changes/archive/2026-03-25-planner-landing-page/design.md diff --git a/openspec/changes/planner-landing-page/proposal.md b/openspec/changes/archive/2026-03-25-planner-landing-page/proposal.md similarity index 100% rename from openspec/changes/planner-landing-page/proposal.md rename to openspec/changes/archive/2026-03-25-planner-landing-page/proposal.md diff --git a/openspec/changes/planner-landing-page/specs/planner-session/spec.md b/openspec/changes/archive/2026-03-25-planner-landing-page/specs/planner-session/spec.md similarity index 100% rename from openspec/changes/planner-landing-page/specs/planner-session/spec.md rename to openspec/changes/archive/2026-03-25-planner-landing-page/specs/planner-session/spec.md diff --git a/openspec/changes/planner-landing-page/tasks.md b/openspec/changes/archive/2026-03-25-planner-landing-page/tasks.md similarity index 100% rename from openspec/changes/planner-landing-page/tasks.md rename to openspec/changes/archive/2026-03-25-planner-landing-page/tasks.md diff --git a/openspec/specs/planner-session/spec.md b/openspec/specs/planner-session/spec.md index 9e20ba9..9f86e40 100644 --- a/openspec/specs/planner-session/spec.md +++ b/openspec/specs/planner-session/spec.md @@ -73,6 +73,21 @@ The Planner SHALL display presence indicators showing which users are currently - **WHEN** a user disconnects from the session - **THEN** their cursor disappears from all other participants' maps within 5 seconds +### Requirement: Planner home page +The Planner home page SHALL explain the tool's purpose and provide a one-click way to start planning. + +#### Scenario: First-time visitor +- **WHEN** a user visits planner.trails.cool for the first time +- **THEN** they see a landing page explaining collaborative route planning, key features, and a prominent "Start Planning" button + +#### Scenario: Start a session +- **WHEN** a user clicks "Start Planning" +- **THEN** a new anonymous session is created and the user is redirected to the session view + +#### Scenario: Journal link +- **WHEN** a user wants to save routes permanently +- **THEN** a secondary CTA links to trails.cool for account creation + ### Requirement: No user data collection The Planner SHALL NOT collect, store, or track any personal user data. Sessions are anonymous by default.