SnapWeb route and display guide

Terminal route

Activate Social Terminal and SnapWeb Builder before this adapter. The plugin creates or adopts a WordPress Terminal page and declares it to SnapWeb as a document route. Add that page to the desired menu. Test direct loading, a navigation click from another SnapWeb page, browser Back/Forward, reload, signed-out access, and signed-in access.

SnapWeb owns navigation, history, metadata, fetching, and document replacement. Social Terminal owns commands, security, markup, and runtime behavior. This adapter owns only exact route matching plus terminal teardown and remount after SnapWeb commits the destination. It uses no iframe and contains no commerce logic.

This Terminal route is the Free baseline. Native routes or SPA behavior contributed by other Cointacted add-ons require Cointacted SnapWeb Pro. Each owning add-on remains responsible for permissions, data, markup, and assets; the bridge supplies only managed pages, route policy, navigation metadata, and lifecycle events.

Administrator map and acceptance test

Use Cointacted → SnapWeb for the Terminal bridge and cross-addon status. Use the owning add-on's settings for its content—for example, Gamification destinations stay under Cointacted → Gamification → Display. Use SnapWeb Builder or the normal WordPress menu editor only to place the resulting canonical page in navigation.

For every enabled Cointacted destination:

1. Open its managed WordPress page directly and confirm meaningful server-rendered content without relying on an earlier SPA visit.
2. Navigate to it from Home and from another add-on route. The persistent SnapWeb header must remain mounted and the URL, document title, menu state, and content must update together.
3. Test browser Back, Forward, refresh, a copied URL, signed-out access, and signed-in access.
4. Disable the destination. Confirm its navigation entry and native route registration disappear without deleting the WordPress page or its saved configuration.
5. Re-enable it and confirm the same page and settings return; a second page or duplicate runtime must not be created.

Official add-on surfaces

Pro discovers supported add-on surfaces at runtime. An enabled surface receives an independent managed WordPress document, exact SnapWeb route, optional navigation item, and mount/unmount lifecycle. Disabling or losing Pro stops native SPA registration without deleting the document or its saved settings, so reactivation is safe.

Add-ons that only contribute Terminal commands do not create empty standalone pages. Their assets join the native Terminal shell through the licensed cross-addon bridge.

Gamification destinations

When Gamification is installed, configure its SnapWeb destinations from Cointacted → Gamification → Display. The flexible Rewards page can contain any enabled sections in administrator-defined order. Focused history, balances, achievements, ranks, achievement catalog, rank catalog, quests, and streaks can each have an independent route and optional navigation entry. Enabling all sections explicitly is the supported all-in-one configuration; there is no hidden “all” mode.

The direct WordPress document remains useful without JavaScript. Pro progressively upgrades reviewed Gamification routes to native no-reload rendering while preserving the same privacy and empty-state policy.

Troubleshooting

• Full reload: confirm the route is the managed Terminal page, SnapWeb public navigation is enabled, and version 1.0.20 or newer is active.
• Blank route: inspect the underlying WordPress page and repair legacy empty content from the display settings.
• Duplicate title: keep one page title in the WordPress document; section titles belong inside a composed Gamification page.
• Stale content after navigation: disable page optimization that delays the adapter bundle and check that another plugin is not replacing the route container.
• Rewards missing: verify Gamification, destination enablement, Pro access for native enhancement, and signed-in visibility settings.

Never put a second terminal or Gamification renderer inside the managed page. The adapter must mount the owning plugin's one canonical runtime.