Features
A complete architecture, not a collection of screens.
Modules share one identity, access model and localization system while remaining independently configurable.Built for a semi-open product
Visitors can understand the product and consume public content, while verified members receive private workflows and operational tools.
Product surfaces
Each area serves a different intent without fragmenting the experience.
Public site
Landing, SEO pages, contact, legal, Blog and indexable community content.
Community layer
Discussions for durable answers and Social for recent activity.
Private app
Dashboard, profile, notifications, support and administration for members.
Operational foundation
Complex workflows are already shaped as coherent modules.
Auth and profile
Email verification, password changes, extended profile and legal acceptances.
Support
Private ticketing, priorities, SLA, attachments and staff roles.
Notifications
Normalized events, email, in-app delivery, preferences and deduplication.
Controlled extensibility
The starter favors explicit configuration and stable contracts.
RO and EN
Separate routes, navigation and content for each language.
Configurable modules
Blog and Social expose runtime state and disappear publicly when unavailable.
Modular growth
Extend one domain without rewriting authentication, layouts or notifications.
See how the modules fit your use case.
Start from a concrete solution, then keep only the surfaces the product needs.