SnapWeb

SnapWeb connects Social Terminal and supported Cointacted add-ons to SnapWeb Builder's persistent public application shell. It uses canonical WordPress documents and SnapWeb's route lifecycle—never iframes or duplicate application runtimes.

Ownership boundary

SnapWeb Builder owns navigation, history, document fetching, metadata, persistent shell layout, and route commits. Social Terminal and each official add-on own their data, permissions, markup, settings, and runtime behavior. This adapter owns exact route matching, managed document publication, route policy, and mount or teardown coordination.

Free and Pro

Free publishes the core Terminal page and supports its native SnapWeb route. The page always has meaningful server-rendered content for direct loads and non-JavaScript fallback.

SnapWeb Pro admits supported official add-on surfaces into the SPA. Each surface receives an independent managed document, route policy, optional navigation entry, assets, and lifecycle. The owning add-on's Pro capability is still checked separately. Losing access removes the native enhancement without deleting the document or saved configuration.

Gamification destinations

Gamification can publish a composed Rewards page with any enabled sections in administrator-defined order. History, balances, achievements, ranks, achievement and rank catalogs, quests, and streaks may also have focused pages. Enabling every section explicitly is the supported all-in-one layout; there is no hidden “all” mode.

Every managed page must work when loaded directly, through SPA navigation, after refresh, and with browser Back or Forward. Signed-in and private routes use session-safe or no-store policies; public routes may be prepared only under their declared policy.

Lifecycle guarantees

Disabling a destination retires its native route and navigation entry without deleting the WordPress page. Re-enabling adopts the same document instead of creating duplicates. Add-ons that contribute only Terminal commands do not receive empty standalone pages.

Start here

Follow installation and route verification, then use the route and display guide to test direct loads, no-reload navigation, session boundaries, managed documents, and Gamification destinations.