docs: align package README taglines for npm and GitHub - #89
Merged
Conversation
Use the final product titles so npm and GitHub package landings share one clear positioning line. Co-authored-by: Cursor <cursoragent@cursor.com>
Keep each product slogan under the heading and move the typed positioning line into the npm/GitHub H1. Co-authored-by: Cursor <cursoragent@cursor.com>
Patch-bump the four published packages so the npm/GitHub README H1 positioning lines ship on the next release. Co-authored-by: Cursor <cursoragent@cursor.com>
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.
Description
Describe the change and the motivation behind it.
Checklist
Testing
pnpm workspace:healthpnpm typecheckpnpm lintpnpm format:checkpnpm test:coveragepnpm buildpnpm package:integritypnpm release:readinesspnpm package:blueprintDocumentation
Describe any documentation updates made or explain why none were needed.
Breaking Changes
List any breaking changes, or state
None.Screenshots
Optional. Add screenshots or recordings when they help explain the change.