Stackbit's control center makes detailed information about your Netlify build available to you via a widget overlay on your web site. It also offers quick access to tools like the your Netlify control panel and GitHub repository. No code is required to install the control center. You can learn more about the control center at https://www.stackbit.com/control-center/.

How do I add the On-page Control Center to my existing Netlify project?

Go to the On-Page Control Center page on the Stackbit site and click the "Pick any Netlify Project." Select the project or projects you want to add the control panel to. Once the projects are updated at Netlify, your On-page Control Panel will be enabled.

How do I add the On-page Control Center to a new Stackbit project?

Any new Stackbit project will include the control panel automatically, so no need to do anything different. Just click the "View Site" button from within the Stackbit Dashboard once your new project has completed building and you should see the control center on the page.

How do I add the On-page Control Center to my existing Stackbit project?

The control center has already been added to all of your existing Stackbit projects. To view the control center on your Stackbit project, go to the Stackbit dashboard and click the "View site" button. This will open the page with the necessary parameters to display the control center. Going forward, you can simply go to your site and the widget will appear.

What does the control center give me?

The initial release of the control center will provide the ability to automatically detect and monitor your Netlify builds, view your build logs, and offer quick links to your Netlify admin and GitHub project page - all from within your website. These are the first features in a toolset we call Stackbit Live. You can learn more about some of the exciting upcoming features here: https://www.stackbit.com/live/

How does the control center work?

Stackbit uses Netlify's snippet injection functionality to inject a small JavaScript file on your page at build time. If you have concerns about how this might impact your site's performance, see then next FAQ item.

Will the control center impact my site's performance?

The Stackbit On-Page Control Center was designed specifically to have a negligible impact on your sites performance by serving from a CDN and avoiding any unnecessary API calls for anyone who is not a Stackbit admin. The initial authentication check happens only when the ?stackbit parameter is added to the site URL. Assuming the user is logged into Stackbit, the status is cached in browser local storage so that subsequent requests do not require either the authentication request or the URL parameter. If both the URL parameter and the local storage do not exist, the control center JavaScript exits.

The control center stopped displaying. What can I do?

The logged in state may be lost if local storage is cleared, the page is open in an "incognito window" or a different browser/device. Go to your Stackbit dashboard and click on the "View Site" button. This will open the page with the proper URL parameter (?stackbit) that triggers the authentication check and displays the control center.

What static site generators does the control center support?

The control center can be added to any site deployed to Netlify regardless of what tool they were built with - even if they weren't built with a static site generator!

What CMS does the control center support?

The Stackbit Control Center will work on any JAMstack site - regardless of whether it uses a CMS or, if it does, which CMS it uses. A link to the connected CMS is available for sites created via the Stackbit site creation tool.

I decided that I don't want the control center. How do I remove it?

We're sorry to hear that. If you imported your project from Netlify, all you need to do is go to your Stackbit dashboard and choose "Remove from Stackbit" for that project. Alternatively, you can go into your Netlify admin and remove the control center snippet from snippet injection. In the meantime, we'd also love to hear from you about how we could make this tool more useful to you.