Align extension page with utility-first reference - #24
Merged
Conversation
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
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 changed
Why
The first extension page introduced a separate product-launch aesthetic and AI-oriented language that did not fit a lightweight utility. This keeps the product presentation restrained and makes the unavailable store installs explicit.
Impact
This changes GitHub Pages documentation only. Extension capture code, permissions, packages, and Mantis Capture are unchanged. Chrome Web Store and signed Safari/App Store distribution remain deferred.
Validation
npm test— 72 passingnpm run types:checknpm run test:browser— all browser smoke assertions passing