Skip to content

Build FleekDash integrations

This guide is for developers who want to build WordPress plugins that integrate with FleekDash: register in the Integrations Hub, add custom routes, and ship their own UI inside FleekDash.

What you can build

  • Third-party integrations: Plugins that call FleekDash\Integration\Registry::register($manifest) and appear in the Integrations Hub.

  • Custom routes: Your integration can register routes (e.g. #/app/your-plugin/dashboard) so users open your UI inside FleekDash.

  • Settings: Define a settings schema (API keys, options) and let users configure your integration from the hub.

Key concepts

  • Registry: Integrations register via the Registry (database). You provide a manifest (id, name, version, integration_type, routes, settings_schema).

  • Manifest: Required fields: integration_id, name, version, integration_type (native | standalone | hybrid), plugin_file. Optional: routes, icon, settings_schema, wp_menu_slug.

  • Routes: Each route has path, title, component_url (HTML/JS entry point), optional icon and permissions. FleekDash loads your page in a sandboxed iframe.

Quick start (developer)

  1. Create a WordPress plugin that, on activation, calls Registry::register($manifest) with your manifest.

  2. Add a routes array with at least one route (path, title, component_url).

  3. Host the HTML/JS for that route (your UI) and load the FleekDash SDK in the page for notifications, navigation, and MessageBus.

  4. Activate your plugin in WordPress; your integration appears in the Integrations Hub. Users can open your route from the app.

Where to go next

  • REST API & SDK: API and SDK reference for endpoints and the JavaScript SDK used inside your integration iframes.

  • How-to guides: Tutorials for step-by-step workflows.

Why build an integration

Registering with FleekDash puts your plugin's UI inside the same fast admin shell your users already work in — no separate wp-admin screen, no jarring design mismatch, and no extra navigation for the user to learn. Agencies that ship client sites benefit twice: the integration looks native in the branded admin they hand over, and settings stay in one predictable place instead of being scattered across top-level wp-admin menus.

The sandboxed iframe model also protects you: your integration's markup and scripts run isolated from FleekDash internals, so updates to either side are less likely to break the other.

For full manifest fields, validation, and examples, see the FleekDash plugin repository docs (production integration system and developer guide).

Was this page helpful?