Feature Overview
Feature Detail
Description
The feature overview page presents a structured showcase of Meander's functional capabilities to prospective organizations browsing the sales website. It organizes features by area or benefit theme - activity registration, accessibility compliance, notifications, expense handling - enabling decision-makers to evaluate fit without login or technical knowledge. The page uses FeatureCardWidget components to present each capability in a scannable, visual format that supports the platform's B2B sales funnel.
Sources & reasoning
Line 224 lists feature overview as a core Sales Website capability alongside the landing page. Both fall under Product Sales Website MVP scope in Fase 1 (lines 335-336), setting target_release to MVP. The blueprint assigns FeatureShowcasePage and FeatureCardWidget to this feature under Product Showcase, confirming it as a distinct deliverable.
-
docs/source/likeperson.md · line 224- Product landing page and feature overview
-
docs/source/likeperson.md · line 335-336**Product Sales Website (MVP scope):** - Statisk landingsside med produktbeskrivelse og fordeler
-
docs/source/likeperson.md · line 220- Purpose: Public information site for prospective organizations - explains what Meander is, shows features, and collects demo requests.
Analysis
Prospective organizations evaluating Meander need to understand the full scope of available capabilities before committing to a demo. The feature overview page reduces uncertainty at the awareness stage. For B2B buyers such as organization administrators at NHF, HLF, and Blindeforbundet, seeing their specific needs - WCAG compliance, bulk registration, encrypted assignments - mapped to concrete product features accelerates purchase decisions. It also serves as a reference during demo calls, grounding sales conversations in documented capabilities rather than verbal claims alone.
Implemented as a static page within the same Next.js static export or Astro site as the landing page, using FeatureShowcasePage as the container and FeatureCardWidget for individual capability cards per the blueprint. Features are defined at build time from a content file - no API calls at runtime. Cards should be organized into thematic groups matching the platform's area taxonomy. The page must meet WCAG 2.2 AA requirements, modeling the accessibility claims made for the product itself. No authentication or backend dependency is required.
Components (6)
Shared Components
These components are reused across multiple features
User Stories
No user stories have been generated for this feature yet.