feat(homepage): landing page with a real call to action, plain copy and good screenshots - #536
Merged
Merged
Conversation
…nd good screenshots Findings E4, P4.5. - Landing rebuilt: split hero with one primary CTA (registration, or "Open your empire" when logged in), "Three things to set up", "What players use most", "And the tools around it", closing band, own footer - en_US homepage copy rewritten without filler words, checked by a test - Header: "Log in" link and "Create account" as the one primary button - Six new 2x WebP screenshots (892 kB total); old PNGs and logos removed - AppFooter hidden on the homepage, which has its own footer Spec: specs/2026-09-30-ui-12-landing-page.md Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
✅ Deploy Preview for prunplanner-preview ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
jplacht
added a commit
that referenced
this pull request
Oct 1, 2026
jplacht
added a commit
that referenced
this pull request
Oct 1, 2026
Up to standards ✅🟢 Issues
|
| Metric | Results |
|---|---|
| Complexity | 0 |
| Duplication | 0 |
🟢 Coverage ∅ diff coverage · +0.00% coverage variation
Metric Results Coverage variation ✅ +0.00% coverage variation (-1.00%) Diff coverage ✅ ∅ diff coverage Coverage variation details
Coverable lines Covered lines Coverage Common ancestor commit (9be4db6) 3515 3424 97.41% Head commit (8c0dcec) 3515 (+0) 3424 (+0) 97.41% (+0.00%) Coverage variation is the difference between the coverage for the head and common ancestor commits of the pull request branch:
<coverage of head commit> - <coverage of common ancestor commit>Diff coverage details
Coverable lines Covered lines Diff coverage Pull request (#536) 0 0 ∅ (not applicable) Diff coverage is the percentage of lines that are covered by tests out of the coverable lines that the pull request added or modified:
<covered lines added or modified>/<coverable lines added or modified> * 100%
NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.
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.
What and why
The landing page had no call to action, generic filler copy ("effortlessly" ×4, "seamless", "stay ahead in the galaxy"), said the same thing twice (Features + Core Concepts) and showed screenshots from before the UI series. Now a visitor understands the app in one screen, sees the tools players use most, and can sign up from the hero.
Changes
tests/locales/homepage.test.ts)AppFooterhidden on the homepage, which has its own footerHow it was verified
pnpm test && pnpm tsc && pnpm lint && pnpm knip: passScreenshots
Desktop (1440)
Mobile (375)
Spec:
specs/2026-09-30-ui-12-landing-page.md(workspace repo)🤖 Generated with Claude Code