fix: match landing page text to actual CLI output and templates#12
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
2 participants
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.
Changes
Every text section now matches the actual
shipkit-pipe --helpoutput and template files:Hero: Tagline/subtext now matches CLI header verbatim. Pill says "Auto-detect + generate".
Dashboard: Replaced fake CI/CD/Health/Security counters with actual generated files: ci.yml, health.yml, AGENTS.md. Config card shows real detected fields (project, platform, PM, Node, scripts).
Features: 6 cards now match the 6 things the CLI actually does.
Terminal demo: Shows actual npx shipkit-pipe dry-run output format.
CI snippet: Fixed actions/checkout@v4 to @v5 to match template.
AGENTS.md snippet: Now shows template format table instead of project-specific content.
Detection table: Columns changed to CI Platform / Package Manager / Has Lint / Has Tests / Has Build / Deploy URL.
How it works: Steps now match actual CLI flow.
FAQ: "What stacks are supported?" now says "Any Node.js >=18".
Meta: Description/OG tags match CLI description.