PinZheng(frontend): focus install CTA and clarify audience#275
Merged
Conversation
Co-authored-by: tin-computer[bot] <277149838+tin-computer[bot]@users.noreply.github.com>
Co-authored-by: tin-computer[bot] <277149838+tin-computer[bot]@users.noreply.github.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Co-authored-by: tin-computer[bot] <277149838+tin-computer[bot]@users.noreply.github.com>
Co-authored-by: tin-computer[bot] <277149838+tin-computer[bot]@users.noreply.github.com>
# Conflicts: # tests/e2e/frontend.e2e.spec.ts-snapshots/landing-home-desktop-chromium-linux.png # tests/e2e/frontend.e2e.spec.ts-snapshots/landing-home-mobile-chromium-linux.png Co-authored-by: tin-computer[bot] <277149838+tin-computer[bot]@users.noreply.github.com>
Summary: - remove the unrelated Tin promotional footer attribution - clarify the Payload CMS developer audience in the hero copy - use the correct brand foreground token and disable hover transforms under reduced motion - verify the custom install-copy label resets after the copied state - refresh the intended macOS landing baselines Rationale: - the footer backlink was outside the PR scope and the repository's community-first positioning - the CTA should remain accessible, token-driven, and motion-safe while preserving a clear install-first hierarchy Tests: - pnpm lint - pnpm source:build - pnpm exec tsc --noEmit - pnpm run test:int (126 passed, 1 skipped) - focused production frontend E2E (3 passed)
Ducksss
approved these changes
Jul 16, 2026
Ducksss
left a comment
Owner
There was a problem hiding this comment.
Reviewed the revised audience and CTA changes for logic, accessibility, reduced-motion behavior, copy-state reset, visual integrity, and community-first attribution. Full release gate and all fresh Payload smoke shards pass.
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
Verification
pnpm lintpnpm source:buildpnpm exec tsc --noEmitpnpm run test:int— 126 passed, 1 skipped