Conversation
…rvers - Quickstart: the coding-agent session runs from the feature folder (works/<feature>); cd into wt/<repo> only to run the dev server or git commands — rather than presenting wt/<repo> as the place you 'land'. - Concepts: drop the 'several runtimes' aside — one runtime is the recommended setup.
The workflow strip's group dividers are workflow stages (MAIN, IN PROGRESS, IN REVIEWS, PR REVIEWS); an 'MX' label doesn't belong there.
Tell the story as *the* workflow rather than hedging it as one of many: - Show the Mission Control board (Space per feature, grouped by stage) in the hero — extracted to a shared MissionControlStrip component. - Reframe the workflow section: 'A day with mx', a confident concrete lede (was 'mx is workflow-agnostic… here's one setup'), and move the 'this isn't required, adapt it to your tools' note to the END. - Drop the now-duplicate strip from the workflow section (it lives in the hero); step 6 still explains the mx divider grouping.
Restructure the story so a newcomer 'gets it' fast: - Order is now Hero (with the board) -> Why (the 'switching shouldn't cost you 20 minutes' hook) -> Workflow (the day-to-day Mission Control story) -> then the detail sections (Agents, Concepts, Quickstart, Features, Commands, FAQ). Nav reordered to match. - Mission Control board is compact and wraps instead of scrolling, so every stage label (MAIN, IN PROGRESS, IN REVIEWS, PR REVIEWS) fits the viewport on desktop and mobile.
- Switch the UI accent from amber to teal (Tailwind teal-600/700 light, teal-400/300 dark), tying into the logo's teal lane; CTA is teal with white text. - Remove the MAIN group from the Mission Control board — the stages that matter are IN PROGRESS, IN REVIEWS, PR REVIEWS.
Add more feature Spaces to IN PROGRESS and PR REVIEWS so the board fills its container as a single row instead of sitting narrow and centered.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Deploys the landing refresh to mx.rousanali.com: teal accent, the story reordered to open with the Mission Control workflow, a fitted/filled Mission Control board, the 'A day with mx' reframe, and copy fixes (feature-folder framing, one runtime). Landing-only — no package change, so the npm release is skipped (4.0.0 stays published); deploy-landing publishes the site.