Skip to content

SnapWeb 1.0.26 / Integrations

Official add-on surfaces in SnapWeb

Admit supported add-on pages into the SPA while preserving product ownership.

SnapWeb Pro admits supported official add-on surfaces. Each receives an independent managed document, exact route, optional navigation entry, asset contract, cache policy, and lifecycle.

The owning add-on keeps responsibility for data, rendering, settings, permissions, and its own Pro features. Both capabilities are checked independently. Losing either removes native enhancement without deleting saved configuration.

Gamification can publish a composed page with explicitly enabled sections in saved order or focused pages for individual sections. Add-ons that contribute only Terminal commands do not receive empty standalone pages.

Enable and test one surface at a time before combining routes.

Was this documentation helpful?Your response helps us improve this page.