feat(marketing): add the Control center section - #12
Merged
Conversation
The decision registry shipped in #9 but the site still sold Gravity on persistence, handoffs and routines alone — nothing said what happens when a bot hits a call it cannot make. The new section makes that the closing argument before the download CTA. The screenshot is the real app against a disposable daemon: five Claude Code sessions across two example projects raised the four decisions themselves, so the waiting list, the via-chain and the deadlines are what the feature actually produces rather than a mock.
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.
What
Adds a Control center section to the marketing site, placed as the closing
argument before the download CTA:
.control) introducing decisions — the options, what each costs,and the recommendation.
.control-shot) showing the real Control center.styles/features.css.Why
The decision registry shipped in #9 and is in the 0.13.0 release, but the site
still sold Gravity on persistence, handoffs and routines alone — nothing said
what happens when a bot hits a call it cannot make. This closes that gap at the
point where a visitor is deciding whether to download.
The screenshot is the real app against a disposable daemon: five Claude Code
sessions across two example projects raised the four decisions themselves, so
the waiting list, the via-chain and the deadlines are what the feature actually
produces rather than a mock.
How tested
pnpm buildinapps/marketing—tsc --noEmitand the Vite productionbuild both pass (6 modules, index.html 9.29 kB / 2.91 kB gzipped).
mainat75a7abb(post-0.13.0); no conflicts.Site-only, so it was deliberately kept out of the v0.13.0 tag — the marketing
site deploys independently of the app build. Follows up #9.
Note
The image is committed at 777 KB. It is
loading="lazy"and below the fold, soit does not affect LCP, but if you would rather it were optimised or served in a
modern format, say so and I will redo it before merge.