Polish the standalone Rockets landing page#43
Merged
Conversation
…sion-page # Conflicts: # components/FloatingNavbar.tsx # components/landing/landing.css # components/landing/sections/Hero.tsx # components/landing/types.ts # src/app/layout.jsx
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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.
Summary
createServer(...)APIWhy
The launch page should show the product before explaining it: one typed domain definition becomes a secure, documented server. The copy and composition now stand on their own, avoid implementation-framework and ecosystem positioning, and make the boundary between Rockets infrastructure and team-owned product code explicit.
Validation
pnpm exec tsc --noEmitpnpm test:site— 22/22 passingpnpm build