Skip to content

Landing: mx demo deck at /deck + deck restructure#26

Merged
rousan merged 9 commits into
mainfrom
develop
Jul 22, 2026
Merged

Landing: mx demo deck at /deck + deck restructure#26
rousan merged 9 commits into
mainfrom
develop

Conversation

@rousan

@rousan rousan commented Jul 22, 2026

Copy link
Copy Markdown
Owner

Deploy-only change (all diffs under apps/landing/**, so the npm release workflow is path-ignored; only the landing site deploys).

What ships

  • New demo deck hosted at mx.rousanali.com/deck — a self-contained slide deck (keyboard/click nav, light/dark, reduced-motion safe).
  • Deck story (23 slides), problem-first: the multi-feature juggle → why a tab/subagent DIY breaks (ports, hydration, multi-repo) → celebration reveal → a large box-and-line system diagram → a mission-control board → the real dashboard screenshot + live "my setup" (hands-on first) → each feature one by one → payoff/close.
  • Generic, outsider-friendly sample names throughout (repo-a…, feature-a…).
  • /deck route: serveDeck dev middleware (vite) + Footer link; GitHub Pages serves public/deck/ directly in prod.

No CLI/core/package changes; no version bump.

rousan and others added 9 commits July 21, 2026 19:00
Add a 15-slide engineering demo deck as a self-contained static page under
apps/landing/public/deck (served at mx.rousanali.com/deck):

- fully deck-driven (diagrams + one real screenshot), keyboard/click nav,
  theme-aware, mx-branded (teal accent, multi-pastel logo)
- uses the real runtime's repos / works / branches / ports and the context
  registry (77 entries) in the diagrams
- covers worktrees, ports, context, archive lifecycle, Mission Control
- a 'why not roll your own?' slide (subagents/tabs clutter vs mx's managed
  works, ports, lifecycle, and shared context)
- ends on a 'my setup' live cue

Also link Deck from the landing footer.
Vite's dev SPA-fallback returned the landing page for /deck and /deck/;
add a dev-only middleware that rewrites those to the deck's index.html.
Also use an absolute image path (/deck/setup-shot.jpg) so the screenshot
loads whether the URL has a trailing slash or not. Production (GitHub
Pages) already serves /deck/ and redirects /deck to it.
- 'See the whole runtime, live': a real mx mission-control screenshot
  (this runtime's works -> services -> ports -> localhost URLs, 49 ports)
- 'Pause a feature, pick it up later': the archive -> unarchive lifecycle
  and session summaries (sessions/*.md) for cold resume
- retitle the macOS Spaces slide to reserve 'mission control' for the
  dashboard. Deck is now 17 slides.
- 'The whole runtime is one folder': an on-disk tree (repos, works/<feature>/wt,
  context, hooks, bin, files) with real names, noting mx owns the structure
- 'A fresh worktree, ready to run': the post-worktree-create hydrate hook
  (copy .env, install deps, seed db, allocate ports) + the lifecycle hook hub

Deck is now 19 slides.
Plainer phrasing on the problem slide for a broader audience.
- Reorder into a pain-first arc: reality -> DIY temptation -> the three
  cracks (ports, hydration, multi-repo) -> celebration reveal -> what is mx.
- Add a celebration reveal slide (confetti burst + rising balloons + logo
  pop), theme-aware and reduced-motion safe.
- Add a concise "What is mx" slide built on the manager-wrap figure.
- Replace all internal repo/work/branch jargon with generic, outsider-
  friendly names (web/api/mobile/worker; checkout-redesign, dark-mode,
  search-filters, refund-flow, e2e-tests).
- Mental model now shows multiple worktrees per work (wt/web + wt/api).
- Enrich the on-disk tree: several pristine repos, works with multiple
  worktrees, context knowledge/conventions/runbooks, hooks, bins, files.
- Ports slide now shows the same app running as three live instances on
  distinct ports, side by side.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
…e names

- Replace the text "What is mx" slide with a system-graph overview: a
  pristine-repos row on top, a works row in the middle (each work box shows
  its agent session, a worktree + branch + port per repo it touches), and a
  central-context band at the base -- so the whole model reads at a glance.
- Switch all sample names to abstract, audience-neutral labels: repo-a..d
  and feature-a..e (was web/api/... and checkout-redesign/...), across every
  slide (reality, DIY, cracks, mental model, tree, unlock, worktrees,
  multi-repo, ports, context, impact).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
- Rebuild the "What is mx" overview as a large box-and-line diagram: a
  pristine-repos box up top, a context-registry box in the top-right corner
  (dashed connector), and five square work boxes across the bottom wired to
  a shared rail. Work boxes now show repos + ports only (branches dropped).
- Add a new "Mission control" slide right after it: a kanban-style board
  grouping the five works by stage (in progress / in review / PR review),
  each card showing its repos, ports, and status -- one view of the fleet.
- Bump slide count to 23; add mobile fallbacks for both new diagrams.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
…ebrow

- Reorder so the audience gets a hands-on feel first: after the mission-
  control diagram come the real dashboard screenshot and the "my setup"
  live slide, and only then the feature-by-feature deep dive.
- Rename the "The unlock" eyebrow (and topic label) to "Parallel agents";
  the slide's h2 title is unchanged.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@rousan
rousan merged commit 601f2e9 into main Jul 22, 2026
3 checks passed
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