feat(landing): build out long-form sales page using existing widgets#693
Open
izzydoesizzy wants to merge 1 commit intoarthelokyo:mainfrom
Open
feat(landing): build out long-form sales page using existing widgets#693izzydoesizzy wants to merge 1 commit intoarthelokyo:mainfrom
izzydoesizzy wants to merge 1 commit intoarthelokyo:mainfrom
Conversation
Replace the Hero + "Coming soon" placeholder at /landing/sales with a complete long-form sales page: hero, brands, problem, solution, benefits, method, stats, testimonials, pricing, FAQs, and final CTA. Uses only widgets already present in src/components/widgets/ and follows the same patterns as src/pages/homes/saas.astro and homes/startup.astro. No new components, styles, or dependencies. Preserves the LandingLayout and the original Hero2 image so the page still fits alongside the other /landing/* demos.
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.
Summary
The
/landing/salespage is currently a placeholder: aHero2plus aCallToActionthat reads "We are working on the content of these demo pages. You will see them very soon." This PR fills it in with a complete long-form sales page that follows the same structure and voice as the fleshed-out home demos (src/pages/homes/saas.astro,homes/startup.astro).Uses only widgets that already live in
src/components/widgets/. No new components, styles, routes, or dependencies. Single file change.Structure
Hero2 → Brands → Content (problem) → Content (solution) → Features → Steps2 → Stats → Testimonials → Pricing → FAQs → CallToAction.
The sections follow the canonical long-form sales arc (hook → problem → solution → proof → method → offer → objection-handling → close), with anchor links so the hero CTA jumps to
#pricingand the secondary CTA jumps to#benefits.Preserved
LandingLayout(matches the 5 sibling landing pages)Hero2image and thematic tagline ("Sell with a story: the long-form way")homes/startup.astroVerification
pnpm check:astro— clean (0 errors, 0 warnings)pnpm check:eslint— cleanpnpm check:prettieron the new file — clean/landing/saleswith all 11 sections, both#pricingand#benefitsanchors resolveNote on CI (pre-existing, not from this PR)
Both CI jobs on
mainare currently red for reasons unrelated to this change:npm run buildfails onsrc/pages/homes/personal.astrobecause it referencesplus.unsplash.com, which is not listed inastro.config.tsimage.domains.npm run checkfails onsrc/pages/index.astrodue to a Prettier formatting drift.Happy to address either in separate follow-up PRs if helpful.
Follow-ups
The other five landing pages (
lead-generation,click-through,product,pre-launch,subscription) are also stubs with the same "coming soon" placeholder. I'd be glad to send follow-up PRs filling those in using the same widget-only approach.