🏠 Overview › 🧩 Components ›🧩 LandingPage

LandingPage

Component Detail

User Interface medium complexity frontend
0
Dependencies
0
Dependents
0
Entities
0
Integrations

Description

The root public-facing page that serves as the primary entry point for prospective organizations evaluating the Meander platform. It assembles all landing page sections into a cohesive, statically exported document optimized for conversion. The page requires no authentication or backend connection and is designed to guide decision-makers toward booking a demo.

Feature: Product Landing Page

landing-page

Sources & reasoning

The source doc explicitly scopes a "statisk landingsside med produktbeskrivelse og fordeler" as MVP for the Sales Website (line 333), and lines 216-225 define the sales website as an information-only public site. The blueprint assigns [MVP] to this feature. Phase 0 action items include "Få opp nettside (Aleksander)" (line 393), confirming this is a launch-blocking deliverable.

  • Purpose: Public information site for prospective organizations - explains what Meander is shows features, and collects demo requests. Scope: Information-only. No authentication, no user accounts, no database, no shared runtime with the operational pr
  • Product Sales Website (MVP scope): Statisk landingsside med produktbeskrivelse og fordeler, Enkelt demo-booking-skjema (sender til e-post/webhook, ingen pålogging), Privacy policy og vilkår

Responsibilities

  • Render the full landing page layout including hero, value proposition, feature showcase, and call-to-action sections
  • Compose and order child sections for a coherent narrative flow targeting organizational decision-makers
  • Provide the demo-booking call-to-action entry point (link or modal trigger)
  • Ensure static export compatibility (Next.js static export, Astro, or plain HTML/CSS)
  • Optimize page structure for SEO and fast initial load without client-side data fetching

Interfaces

LandingPage(): JSX.Element
getStaticProps(): StaticProps