c7c1c275df
Proposed changes (all with proposal, design, specs, tasks): - app-navigation (9 tasks) — nav bars for both apps - planner-landing-page (7 tasks) — standalone landing page - planner-multiplayer-awareness (13 tasks) — participants, cursors, names - changelog (13 tasks) — public changelog with "what's new" - transactional-emails (15 tasks) — magic link + welcome emails - planner-features (18 tasks) — no-go areas, notes, recovery, rate limits - komoot-import (23 tasks) — Komoot tour import - route-features (37 tasks) — sharing, multi-day, spatial, photos Also adds docs/old-trails-analysis.md with feature analysis from the older trails project. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
30 lines
1.1 KiB
Markdown
30 lines
1.1 KiB
Markdown
## ADDED Requirements
|
|
|
|
### Requirement: Route visibility levels
|
|
Routes SHALL have a visibility setting controlling who can see them.
|
|
|
|
#### Scenario: Private route
|
|
- **WHEN** a route's visibility is "private"
|
|
- **THEN** only the owner can view it
|
|
|
|
#### Scenario: Public route
|
|
- **WHEN** a route's visibility is "public"
|
|
- **THEN** anyone can view it and export its GPX
|
|
|
|
### Requirement: Share routes with specific users
|
|
Route owners SHALL be able to share routes with specific users at view or edit permission levels.
|
|
|
|
#### Scenario: Share with view access
|
|
- **WHEN** owner shares a route with another user as "view"
|
|
- **THEN** that user can see the route and export GPX but cannot edit
|
|
|
|
#### Scenario: Share with edit access
|
|
- **WHEN** owner shares a route with another user as "edit"
|
|
- **THEN** that user can start Planner sessions and create new versions
|
|
|
|
### Requirement: Fork routes
|
|
Users SHALL be able to fork (copy) public routes to their own collection.
|
|
|
|
#### Scenario: Fork a public route
|
|
- **WHEN** a user clicks "Fork" on a public route
|
|
- **THEN** a copy is created in their collection with the original credited
|