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) <noreply@anthropic.com>
This commit is contained in:
parent
4ddaad8c5f
commit
160079b9be
6 changed files with 15 additions and 0 deletions
|
|
@ -0,0 +1,2 @@
|
|||
schema: spec-driven
|
||||
created: 2026-03-25
|
||||
|
|
@ -0,0 +1,44 @@
|
|||
## Context
|
||||
|
||||
The Planner home page is currently a centered heading ("trails.cool Planner")
|
||||
and subtitle. It has no CTA, no explanation, and no way to start. Users must
|
||||
know to visit `/new` to create a session.
|
||||
|
||||
## Goals / Non-Goals
|
||||
|
||||
**Goals:**
|
||||
- Explain what the Planner does in 5 seconds of reading
|
||||
- One-click session creation (no signup, no form)
|
||||
- Feature highlights: collaborative, BRouter routing, elevation, GPX export
|
||||
- Link to Journal for users who want accounts and saved routes
|
||||
- i18n (English + German)
|
||||
- Fast load, SSR-friendly, no heavy JS
|
||||
|
||||
**Non-Goals:**
|
||||
- Marketing copy or elaborate graphics
|
||||
- Pricing or plans
|
||||
- User testimonials
|
||||
- Interactive map demo on the landing page (too heavy)
|
||||
|
||||
## Decisions
|
||||
|
||||
### D1: Single-page component in home.tsx
|
||||
|
||||
No new route — rewrite `apps/planner/app/routes/home.tsx`. The page is static
|
||||
content + a CTA link to `/new`. No loader needed.
|
||||
|
||||
### D2: Feature cards with icons
|
||||
|
||||
Show 4-5 feature highlights as simple cards: collaborative editing, route
|
||||
profiles, elevation profile, GPX export, no account needed. Use Tailwind —
|
||||
no icon library, just emoji or simple SVG.
|
||||
|
||||
### D3: Link to Journal as secondary CTA
|
||||
|
||||
"Want to save your routes? Create a free account on trails.cool" — links to
|
||||
the Journal. This bridges the two apps without requiring Journal for basic use.
|
||||
|
||||
### D4: Footer with legal and links
|
||||
|
||||
Privacy link (points to Journal's /privacy), GitHub repo, "Built with
|
||||
BRouter and OpenStreetMap" attribution.
|
||||
|
|
@ -0,0 +1,34 @@
|
|||
## Why
|
||||
|
||||
The Planner at planner.trails.cool should work as a standalone product — anyone
|
||||
can visit, understand what it does, and start planning a route without needing
|
||||
the Journal. Currently the home page is a blank heading with no explanation and
|
||||
no way to start. Visitors bounce immediately.
|
||||
|
||||
## What Changes
|
||||
|
||||
- Replace the Planner home page with a landing page that explains the tool:
|
||||
collaborative route planning, BRouter routing, GPX export, no account needed
|
||||
- Prominent "Start Planning" CTA that creates a new session
|
||||
- Brief feature highlights (collaborative editing, routing profiles, elevation,
|
||||
GPX export)
|
||||
- Footer with links to trails.cool Journal, privacy page, GitHub repo
|
||||
- The landing page should load fast — no heavy assets, SSR-friendly
|
||||
|
||||
## Capabilities
|
||||
|
||||
### New Capabilities
|
||||
|
||||
(None — this replaces an existing page with useful content.)
|
||||
|
||||
### Modified Capabilities
|
||||
|
||||
- `planner-session`: Home page becomes a landing page with session creation CTA
|
||||
- `map-display`: Landing page may show a decorative map or screenshot
|
||||
|
||||
## Impact
|
||||
|
||||
- **Files**: `apps/planner/app/routes/home.tsx` (complete rewrite), i18n keys
|
||||
- **Dependencies**: None
|
||||
- **Design**: Needs to look good — this is the first impression for standalone
|
||||
Planner users
|
||||
|
|
@ -0,0 +1,16 @@
|
|||
## MODIFIED Requirements
|
||||
|
||||
### 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
|
||||
|
|
@ -0,0 +1,16 @@
|
|||
## 1. Landing Page Content
|
||||
|
||||
- [x] 1.1 Rewrite Planner home.tsx with hero section: heading, subtitle, "Start Planning" CTA linking to /new
|
||||
- [x] 1.2 Add feature highlights section (4-5 cards): collaborative editing, routing profiles, elevation profile, GPX export, no account needed
|
||||
- [x] 1.3 Add secondary CTA: "Save your routes on trails.cool" linking to Journal
|
||||
- [x] 1.4 Add footer: privacy link, GitHub repo, BRouter/OSM attribution
|
||||
|
||||
## 2. i18n
|
||||
|
||||
- [x] 2.1 Add all landing page strings to en.ts and de.ts (hero, features, CTAs, footer)
|
||||
|
||||
## 3. Verify
|
||||
|
||||
- [x] 3.1 Verify landing page renders correctly at planner.trails.cool
|
||||
- [x] 3.2 Verify "Start Planning" creates a session and redirects
|
||||
- [x] 3.3 Update E2E planner test if home page assertions changed
|
||||
Loading…
Add table
Add a link
Reference in a new issue