Skip to content

docs: plan an icon rail with Home, pinned Spaces and Settings - #2113

Draft
Douglasymlai wants to merge 1 commit into
mainfrom
docs/app-shell-rail-plan
Draft

Douglasymlai wants to merge 1 commit into
mainfrom
docs/app-shell-rail-plan

Conversation

@Douglasymlai

Copy link
Copy Markdown
Contributor

Pull Request

Related Issue

N/A — maintainer-directed work; no linked issue required for this PR.

Description

Draft. This branch only adds the plan, docs/app-shell-rail-plan.md. The implementation will follow in the pull requests listed in §10 of the plan.

Problem

Today the app has a Space page and a Home page that also holds Settings. People move between them with the Home button and the Space switcher in the top bar. Nothing on screen shows which other Spaces have running work or are waiting for a reply, and starting a Session means first going into a Space.

Approach

Add an icon rail on the far left with three kinds of places:

  • Home: the overview of every Space and its Sessions. People start a New session here and can open any Session in place. Clicking a Space's name shows its details, like today's Space page.
  • Pinned Spaces: a Space someone keeps working in can be pinned to the rail. Its tile opens the Space view with Files, Dispatch, Automations and its Sessions, and shows a dot when work is running or waiting for a reply.
  • Settings: app-wide setup, moved out of Home into its own page again.

The top bar keeps only window buttons and layout controls. The plan also compares two other layouts that were considered, lists the behaviour rules, routes, design-system notes and open questions, and splits the work into four pull requests that land after the split view work (#2069, #2071).

Testing

Not started. This branch only adds the plan document, which passes the repository's Prettier check. Testing will follow §11 of the plan.

Testing Evidence (REQUIRED)

  • I have included human-verified testing evidence in this PR.
  • This PR includes frontend/UI changes, and I attached screenshot(s) or screen recording(s).
  • No frontend/UI changes in this PR.

Not yet available: the branch currently contains only the plan document.

What is the purpose of this pull request?

  • Bug fix
  • New Feature
  • Documentation update
  • Other

Contribution Guidelines Acknowledgement

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant