refactor: simplify settings routing to one surface #296

New issue

Closed

opened 2026-05-11 18:30:40 +00:00 by barrettruth · 0 comments

barrettruth commented

2026-05-11 18:30:40 +00:00

Owner

Problem

Settings currently has both modal-intercepted routes and full-page routes for the same sections.

That gives a nice interaction model, but it doubles route surface and makes scope cuts more expensive because every settings section exists in two route trees.

Solution

Choose one settings navigation surface for v0.1.0 and remove the duplicate route mode.

Preferred solution: keep normal /settings/* pages because they are simpler, linkable, and easier to reason about. Remove the intercepted @modal/(.)settings/* routes unless there is a concrete workflow that requires them.

Acceptance criteria

Each settings section has one route implementation.
Navigation to settings remains predictable from queue, kanban, and calendar.
Browser back/forward behavior stays understandable.
Removed settings sections from other issues do not need duplicate route cleanup.

## Problem Settings currently has both modal-intercepted routes and full-page routes for the same sections. That gives a nice interaction model, but it doubles route surface and makes scope cuts more expensive because every settings section exists in two route trees. ## Solution Choose one settings navigation surface for v0.1.0 and remove the duplicate route mode. Preferred solution: keep normal `/settings/*` pages because they are simpler, linkable, and easier to reason about. Remove the intercepted `@modal/(.)settings/*` routes unless there is a concrete workflow that requires them. ## Acceptance criteria - Each settings section has one route implementation. - Navigation to settings remains predictable from queue, kanban, and calendar. - Browser back/forward behavior stays understandable. - Removed settings sections from other issues do not need duplicate route cleanup.

barrettruth added this to the v0.1.0 milestone

2026-05-11 18:30:40 +00:00

barrettruth added the

track:ui

type:cleanup

labels

2026-05-11 18:30:40 +00:00

barrettruth referenced this issue

2026-05-11 18:31:12 +00:00

v0.1.0 roadmap: single-user self-hosted launch #144

barrettruth referenced this issue from a pull request that will close it,

2026-05-11 18:54:25 +00:00