Skip to main content
AnotherWrapper does not only ship app dashboards. It also includes a complete public-facing marketing page so you are not starting from a blank screen when it is time to sell the product.

​
What This Page Is

The landing page is the public marketing site for your product. Its job is to:
  • explain what the product does
  • show the app surface
  • build trust
  • answer common objections
  • present pricing
  • push visitors toward checkout or signup
That means it is not “just design”. It is part of the product and part of your sales funnel.

​
Current Structure In This Repo

The landing page route is:
  • app/landing/page.tsx
That page assembles reusable sections from:
  • components/landing/navbar.tsx
  • components/landing/hero.tsx
  • components/landing/logos.tsx
  • components/landing/features.tsx
  • components/landing/apps-showcase.tsx
  • components/landing/how-it-works.tsx
  • components/landing/testimonials.tsx
  • components/landing/pricing.tsx
  • components/landing/faq.tsx
  • components/landing/cta.tsx
  • components/landing/footer.tsx
So if you want to change the marketing site, you usually do not need to rewrite one giant page. You edit the section that owns the content you care about.

​
What The Landing Page Already Covers

The current site already talks about:
  • the AI app bundle
  • auth, payments, analytics, email, storage, and SEO
  • supported providers
  • pricing tiers
  • testimonials
  • FAQs
In other words, the repo already includes a usable marketing base, not just a developer playground.

​
Why This Matters

A lot of starter kits give you the app shell but leave the marketing site as an afterthought. This repo gives you both:
  • the internal product experience
  • the public page that sells the product
That makes it much easier to launch quickly, run ads, share on social, or test new positioning without building a separate marketing project.

​
What You Will Usually Customize First

Most teams update these things first:
  • headline and subheadline in the hero
  • featured app screenshots and descriptions
  • pricing copy
  • FAQ answers
  • CTA button copy and links
  • social proof and logos
  • footer links
If you are rebranding AnotherWrapper into your own SaaS, this is the part you will almost certainly touch on day one. The landing page is connected to several other systems in the repo:
  • SEO for metadata, sitemap, and OG images
  • Analytics for visitor tracking
  • Payments for pricing and checkout flows
  • Email for lead capture and lifecycle follow-up
  • Meta Ads if you want paid acquisition attribution
That is why keeping the landing page inside the same repo is useful. Your marketing site and product infrastructure can evolve together.

​
Good Beginner Workflow

If you are new to code, here is the safe order to customize it:
  1. update the copy before changing the layout
  2. replace screenshots and app descriptions so they match your offer
  3. update pricing and checkout links
  4. confirm analytics and email flows are connected
  5. only then start redesigning sections
This reduces the chance that you spend hours on styling before the basic business flow is actually correct.

​
Common Mistakes

  • changing the visuals but leaving old app names and feature claims behind
  • updating pricing copy without checking the real checkout links
  • forgetting to add analytics before launching traffic
  • treating the landing page as separate from SEO, email, and payments
  • shipping a beautiful page that still talks about features your product no longer has

SEO

Keep metadata, sitemap, and OG images aligned with the landing page.

Analytics

Track which sections and CTAs are actually working.

Payments

Connect pricing sections to real checkout flows.