Multiple platforms
One install template, the right step-by-step guide for every platform.
Your installers arrive on all sorts of platforms — WordPress, Shopify, Webflow, Squarespace, and more. You don't build a separate guide for each. You build one install template, and Inboard resolves it into platform-specific steps for whoever opens the widget.
Auto-detection
When the widget loads, it detects the installer's platform automatically and presents the guide tailored to it. For most installers this is invisible: they open the widget and immediately see steps written for the platform they're already on, with no platform picker to think about.
How one template serves many platforms
You author an install template as a set of requirements — paste a code snippet, add a DNS record, enter an API key, and so on. Each requirement knows how to resolve itself for the detected platform: the same "paste this snippet" requirement becomes the right place and procedure for WordPress, and a different but equivalent procedure for Shopify. You describe what must happen once; Inboard turns it into the how per platform.
This means a single install template stays in sync everywhere. Update a requirement and every platform's guide reflects the change — there are no parallel copies to keep aligned.
When a platform isn't detected
Auto-detection can't always tell — some sites are custom-built, or the installer is configuring something from a different machine than the one being set up. In that case the widget falls back to explicit selection: the installer picks their platform from the supported list, and the guide resolves to that choice. The host page can also force a specific platform up front when it already knows which one applies.
A data-driven catalog
The set of supported platforms is data-driven, not hard-coded into the widget. The catalog is expandable, so support for additional platforms can be added without you rebuilding your install template — your existing requirements simply resolve onto the new platform when it lands.
Where to go next
- The widget — how the embeddable UI detects platforms and renders the guide.
- Install templates — author the requirements that resolve into per-platform steps.