Repository navigation
Fix/lui 150 prepare landing page to live deploy - #103
Merged
Merged
Conversation
- Deleted the LandingFooter component from the landing section. - Removed footer-related translations from both English and French JSON files.
- Changed the call-to-action label from "Get early access" to "Create your account" in the main section and the final section of the home page.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Strive PR Agent ReviewThe review could not be generated for this run (model unavailable or rate-limited). Push again to retry. |
luidgi-dev
deleted the
fix/lui-150-prepare-landing-page-to-live-deploy
branch
September 20, 2026 13:17
5 tasks done
This branch was successfully deployed
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
Removes the pre-launch framing from the landing page ahead of the v1.0.0 release.
CTAs
Both primary CTAs read "Get early access", which announced a waitlist behind a
closed door while the product is open. They now read "Create your account".
The same label is used in the hero and in the closing section on purpose: both
point at the same destination, so two different labels would suggest two different
actions.
"Create your account" rather than "Get started" because the hero stacks it directly
above "Try the demo". One creates something, the other looks around, and the
contrast has to be readable at a glance. "Get started" next to "Try the demo" reads
as two ways of browsing.
Not used, and why: "Find your rhythm" is already the headline of the closing
section, so it would repeat itself a few centimetres apart. "Start your arc"
borrows The Arc, which
docs/UX_WRITING.mddefines as the twelve-week consistencyview on a ritual detail page; using it as a sign-up verb blurs a canonical term.
Dead code carrying pre-launch copy
components/landing/landing-footer.tsxis never rendered. It is only re-exportedfrom the barrel, and it renders a
LogoutButtonin the footer of a public landingpage, which is a leftover from an earlier version. It carried the last three
strings saying the app had not shipped:
landing.hero.cta: "Available soon" / "Bientôt disponible"landing.footer.thanks: "the application is coming soon" / "L'application arrivetrès bientôt"
The component, its export and those keys are removed from both message files.
Kept on purpose
settings.unlockSheet.lifetimeBullet2, "Early access to new features", is alifetime plan benefit, not beta branding. Renaming it would change a commercial
promise.
Verified
tsc --noEmit, ESLint, 83 Vitest tests andnext buildall pass. A grep forearly access,beta,coming soon,available soon,waitlistand their Frenchequivalents returns nothing in the landing copy.
Part of LUI-150