One operating system for community, content and commerce.
This reference turns the recovered Merkos product into a navigable system specification. It documents source-confirmed capabilities, workflows, runtime behavior and integration boundaries while explicitly separating active behavior from incomplete, disabled and uncertain legacy code.
Navigate by system, not legacy screen.
Each page is organized around the product contract: what an operator or end user can do, how the workflow behaves, what it depends on, and what remains unresolved. The same navigation is available on every documentation route.
Configurable reporting, exports and inline operational actions.
Visual builder, runtime composition, security, data binding and responsive behavior.
Tickets, conditional registration, forms, allocations, confirmation and automations.
Nested form builder, reusable questions, rules, processing and CRM-backed inputs.
Flows, conditional groups, server actions, client actions and workflow screens.
Catalog, cart, checkout, orders, payments, donations and fulfillment.
Records, profiles, memberships, enrollments, saved views and pairing.
Files, Dropbox, media, courses, progress, posts and resources.
Broadcasts, visual email composition, discussions, chat, Zoom and realtime.
Vaults, stored value, funding, generated codes and transaction history.
Admin runtime, domains, facilities, assets, users, logs and system modeling.
Provider accounts, OAuth, localization and reusable platform configuration.
Capabilities compose across product boundaries.
Merkos is not a collection of isolated modules. Sites embeds Events, Forms, Commerce, CRM, Courses, Programs, Communications and provider-backed components; workflows reuse the same rule and value-binding systems.
Preserve capability. Simplify presentation.
Editors, selectors, actions, renderers and runtime dependencies are followed before a legacy surface is retired.
The product specification is the union of primary and v3 source. Matching files establish parity; differences remain explicit.
Source bugs and misleading labels are recorded as anomalies rather than reproduced as intended product behavior.