Product Landing Page
Feature Detail
Description
The product landing page is the primary public-facing entry point for the Meander platform's sales website, targeting prospective organizations. It presents the platform's value proposition, key capabilities, and call-to-action for demo booking through a hero section and benefit-focused content. As a static page with no authentication or backend dependency, it is designed for fast load times, converting first-time visitors into qualified demo requests through clear, benefit-oriented messaging.
Sources & reasoning
The source doc explicitly lists a static landing page under Product Sales Website MVP scope in Fase 1 (lines 335-336), establishing target_release as MVP. Line 224 confirms product landing page as a core sales site capability. The blueprint assigns LandingPage and HeroSectionWidget components to this feature under Product Showcase.
-
docs/source/likeperson.md · line 335-336**Product Sales Website (MVP scope):** - Statisk landingsside med produktbeskrivelse og fordeler
-
docs/source/likeperson.md · line 224- Product landing page and feature overview
-
docs/source/likeperson.md · line 219**Product 4: Product Sales Website** (simple static site)
Analysis
The landing page is the first touchpoint for prospective organizational clients evaluating Meander - NHF, HLF, Blindeforbundet, and similar nonprofits. A clear, benefit-focused landing page drives demo bookings, which are the platform's primary acquisition channel. By surfacing operational benefits - reduced reporting burden, WCAG 2.2 AA compliance, BankID integration - the page shortens the sales cycle for B2B buyers. It builds credibility with organization administrators who evaluate digital tools based on reliability, compliance, and fit for volunteer management workflows.
Implemented as a static site (Next.js static export, Astro, or plain HTML/CSS) with no backend dependency, deployed on Vercel or equivalent static hosting. The hero section uses the HeroSectionWidget component from the blueprint, with LandingPage as the top-level container. Full SEO metadata (Open Graph, title tags, structured data) is required for organic discoverability. The page must be mobile-first and load quickly since prospective org admins may encounter it on mobile. No authentication, database access, or API calls are made from this page.
Components (6)
Shared Components
These components are reused across multiple features
User Stories
No user stories have been generated for this feature yet.