Establish and pilot the PortOS admin workspace design system
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- javascript, react
Research direction
Start with docs/UX_DESIGN_GUIDE.md and docs/UX_DESIGN_AUDIT.md, then read child issues #7792–#7797 and the specification PR #7798. Confirm the specification prerequisite before reviewing each pilot. Done means the child acceptance criteria and bounded Settings, Brain and Apps audit are complete while preserving desktop/mobile navigation, existing routes and runtime behavior.
Written by the indexing model from the issue text.
Description
Design specification: PR #7798.
Problem / Goal
Rich admin pages mix configuration, setup, reference prose, tools and results in long documents, while horizontally overflowing and nested navigation hide useful destinations. Establish reusable task-focused workspace patterns and implement a bounded first rollout.
Reviewed design
The design-spec PR will add docs/UX_DESIGN_GUIDE.md and docs/UX_DESIGN_AUDIT.md, plus an entry in client conventions. Preserve icon-prefixed desktop navigation and the CoS-style mobile icon row. Grouped sheets may supplement discovery but must never replace fixed mobile icon navigation. The earlier text-only exploratory mockup is not the navigation contract.
Use six page families, desktop related-work/evidence columns, results-first information placement, short contextual explanations, named task views, existing drawers, and explicit asynchronous state. Keep URLs, provider-consent gates, saved-state behavior, model semantics and privacy intact.
Scope and sequence
- Models navigation foundation, including cross-prefix hosts.
- Jev task-view pilot.
- Performance comparison/evidence pilot using the proven layout.
- Runtimes operations roster and CoS queue-first task layout.
- A bounded evidence-based Settings/Brain/Apps audit and linked follow-up backlog.
Implementation checklist:
- #7792 — Expose Models destinations in a grouped navigator while preserving desktop and mobile icons
- #7793 — Turn Jev into focused task views with side-by-side scoring and evidence
- #7794 — Make Model Performance results-first with focused test views and selected evidence
- #7795 — Reshape Runtimes around a consistent operations roster and selected configuration
- #7796 — Make CoS Tasks queue-first while retaining persona and icon navigation
- #7797 — Audit Settings, Brain and Apps against the adopted workspace patterns and file scoped follow-ups
This epic is a coordination item, not an implementation claim. Do not close it when the documentation PR merges.
Acceptance criteria
- The reviewed guide/audit are merged and linked from client conventions and docs index.
- Models navigation, Jev, Performance, Runtimes and CoS pilot issues meet their acceptance criteria.
- Desktop icons and mobile icon rows survive across all pilots, including keyboard/focus, names, selection and overflow behavior.
- Shared components are extracted only from proven repetition; current routes, aliases, runtime semantics and explicit provider actions remain compatible.
- Before/after task checks and responsive evidence use synthetic data and distinguish observed usability from hypotheses.
- The bounded follow-up audit produces concrete deduplicated work for Settings, Brain and Apps; it does not claim every PortOS page has been redesigned.
Delivery policy
Every child waits for the specification PR to merge. Further dependencies are explicitly identified as foundation or rollout sequencing; the blocked label is removed only after that child's prerequisites are met. Preserve readable dependency links in each child. No broad global CSS replacement, backend behavior change, or live-instance data in artifacts.
- Dominant language
- JavaScript
- Stars
- 38
- Forks
- 32
- Avg merge
- 50m
- Merged PRs (30d)
- 985
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from atomantic/PortOS
-
blocked effort:high enhancement model:medium plan
Difficulty 5/5 Over a week Newbie friendliness 42/100
-
blocked effort:high enhancement model:heavy plan
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
blocked effort:high enhancement model:medium plan
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
blocked effort:high enhancement model:heavy plan
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
effort:high enhancement in-progress model:heavy plan
All issues in atomantic/PortOS
Similar issues
-
code-quality refactoring
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
github/gh-aw-firewall#8816 ·
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
optimization optimization:agents-md-curator
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
githubnext/gh-aw-cao#13143 ·
-
status: needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100