Feature Overview
Feature Detail
Description
The Feature Overview page provides prospective organizations with a structured, scannable presentation of Meander's full capability set, organized by functional area (the canonical area taxonomy from the source doc). It allows decision-makers to quickly assess which modules are relevant to their organization's needs and understand the module-toggle model - that capabilities are selectively enabled per tenant rather than delivered as an all-or-nothing package. The page is static, public, and requires no authentication. It maps directly to the area taxonomy defined in section 8 of the source documentation, covering Mobile App areas, Admin Web Portal areas, and optionally noting which features are phase-gated (MVP vs. later releases). This gives buyers a roadmap view alongside the current feature set, supporting longer sales conversations with technically involved stakeholders.
Sources & reasoning
The source doc explicitly lists "feature overview" as a core Sales Website capability alongside the landing page, both in the product description and implicitly in the MVP scope for the sales site. Blueprint marks it [MVP]. Phase 1 ordinal maps to MVP. The feature overview supports the self-qualification need evident from the multi-organization, divergent needs context throughout the source doc.
No source references — this artifact was included based on reasoning alone (see above).
Analysis
Prospective organizations - particularly those with technically involved decision-makers or procurement committees - need more than a marketing summary. The Feature Overview page bridges the gap between the high-level landing page and a full sales demo, allowing organizations to self-qualify based on their specific module needs (e.g., Blindeforbundet evaluating encrypted assignments, HLF evaluating course administration and expense reimbursement). By presenting capabilities in the canonical area structure, the page also reduces confusion during onboarding: terms and groupings the buyer saw on the website match exactly what they encounter in the Admin Web Portal's Feature Toggles screen. This vocabulary alignment shortens the onboarding learning curve and reduces support load for the Norse Digital Products team after contract signature.
Implemented as a static page within the same sales website deployment as the Product Landing Page. Content is derived from the canonical area taxonomy (section 8 of source doc) and must stay synchronized with the actual module toggle registry - any area added to the operational products should eventually appear here. In practice, synchronization is manual at MVP given the static build approach; a future improvement could generate this page from a shared taxonomy file. The page requires no backend calls, no authentication, and no shared runtime. Visually, it should group features by area with brief descriptions of each, indicate which are always-on vs. togglable, and note phase availability where relevant. WCAG 2.2 AA compliance is required throughout since this is a public-facing page for an accessibility-focused platform.
Components (44)
Shared Components
These components are reused across multiple features
Service Layer (11)
Data Layer (23)
Infrastructure (7)
User Stories
No user stories have been generated for this feature yet.