Goal
Unify and stabilize the core UX for the SimuCLI dashboard, demo creator/editor, embed runtime, and docs. This epic groups 21 targeted issues into phased work so we can deliver high-impact improvements quickly.
Phasing (P0 = highest priority)
P0 (quick fixes and blockers — target 1-2 sprints)
- Fix search functionality (dashboard + docs) — reliable, states, routing.
- Implement library/analytics actions — ensure buttons route/work.
- Fix guide/logs routing — guide should open in-context; logs route correctly.
- Terminal color persistence — persist settings and reflect in embed.
- Settings page & wiring — make Settings reachable and functional.
P1 (experience & consistency — next 2-3 sprints)
- Simplify dashboard layout — reduce clutter, prioritize actions.
- Add page/loading animations and skeletons — improve perceived performance.
- Unify dashboard/editor aesthetics — shared styles and components.
- Standardize terminal components across creator/embed/user views.
- Profile & account actions + GitHub avatar — functional menu and avatar.
P2 (polish, features, design)
- Redesign demo creator to be drag-and-drop (scratch-style).
- Implement embed mini guide and ensure guide parity with user view.
- Fix asciinema import flow and add import fixtures/tests.
- Increase base font size and fix docs typography.
- Improve docs search UI and add lock indicators for missing docs.
- Create logo/mascot and apply brand assets.
- Fix small UX items: library/analytics deeper pages, header/quick settings, remove/clarify "admin" label.
Deliverables per phase
- P0: deployable fixes (bugfix PRs), tests for search and routing, small UX tweaks.
- P1: design tokens, component library updates, refactors for shared components.
- P2: design assets, larger UX flows, and documentation updates.
Acceptance Criteria (Epic-level)
- Dashboard and editor allow reliable authoring, preview, and publishing.
- Embedded runtime matches creator preview for terminal visuals.
- Docs and search are readable and usable with clear locked placeholders.
- Core header/settings/profile flows are discoverable and functional.
Next steps
- Create individual GitHub issues (done drafts) and link them to this epic.
- Triage and label each issue with P0/P1/P2, estimate, and assign owners.
- Start P0 work: pick top 1-2 issues, open PRs, and run integration checks.
Linked issues (drafts to create/link)
- Search is unreliable in dashboard and docs search UX needs polish
- Dashboard layout is cluttered and needs simplification
- Library and Analytics buttons are non-functional
- Missing loading/transition animations between pages and major state changes
- Create proper brand identity (logo/mascot) and apply consistently
- Unify visual aesthetics between dashboard and demo editor/creator
- Terminal experiences are inconsistent across creator, embed, and user view
- Guide and logs buttons are mapped incorrectly and missing correct page definitions
- Ascii cinema import flow is not working correctly
- Typography is too small and inconsistent across app and docs
- Terminal color settings do not persist or propagate to embedded runtime
- Demo creator should be simplified into a scratch-style drag-and-drop builder
- Embed mini guide is missing and inconsistent with terminal mini guide behavior
- Settings and profile actions are non-functional; GitHub avatar should be used
- Add lock indicator for docs that are not yet implemented
- Guide should open in user and embed views instead of redirecting to docs
- Implement functional settings page and wire all settings entry points
- Account/profile interactions are non-functional and must support GitHub avatar + actions
- Remove or clarify confusing "admin access" label in profile area
- Create consistent global header with quick settings accessible from all key screens
- Docs search UI needs visual and usability polish (functionality exists)
Goal
Unify and stabilize the core UX for the SimuCLI dashboard, demo creator/editor, embed runtime, and docs. This epic groups 21 targeted issues into phased work so we can deliver high-impact improvements quickly.
Phasing (P0 = highest priority)
P0 (quick fixes and blockers — target 1-2 sprints)
P1 (experience & consistency — next 2-3 sprints)
P2 (polish, features, design)
Deliverables per phase
Acceptance Criteria (Epic-level)
Next steps
Linked issues (drafts to create/link)