Is Stackbit FREE?
Stackbit is currently in beta and all of the publicly available services are free.
- The site builder is and will remain free to use. Any sites generated using it are yours to keep - we will not charge for them. As we do not host the site, maintain the CMS or control the code, you are free to do what you wish with the site.
- Stackbit itself is a collection of services that enable services like on-page editing and maintaining sites. Portions of this service are paid and currently in private beta. However, every Stackbit generated site has a widget that is automatically enabled that allows viewing things like deploy status, deploy logs on page. This entry-level functionality is and will remain free.
What does Stackbit do?
Stackbit encompasses a variety of services that enable on-page content management and site management. Currently these include the ability to edit content directly on the page, add new or duplicate existing pages, share live or snapshot previews of content changes and monitor site builds. Stackbit Live also supports teams via collaborator access and built-in workflow. Our plan is to continue to expand the features and capabilities of the tool to enable it to be your "one stop shop" for managing your site.
What CMS does Stackbit support?
The goal of Stackbit is to support any site, regardless of which headless CMS they choose. However, at this stage of development we currently support Contentful, Sanity and Forestry. If your company has a different set of requirements, we still encourage you to request early access and we'd be happy to explore how we can address your needs.
What Static Site Generator does Stackbit support?
The goal of Stackbit is to support any site, regardless of what tools were used to build them. However, at this stage of development we currently support sites built with Gatsby, Next.js and Hugo with support for Jekyll on the near term roadmap. If your company has a different set of requirements, we still encourage you to request early access and we'd be happy to explore how we can address your needs.
What deployment options does Stackbit support?
The goal of Stackbit is to support any site, regardless of where and how you deploy it. At this stage of development we are optimized for deployments to Netlify but are capable of supporting a variety of other options. We encourage you to request early access and we're happy to explore how we can address your needs.
What do I need to do to support Stackbit?
Why are you requesting [enter scary looking permission] from my GitHub account?
When you create a project on Stackbit, we create a new git repository and push your newly generated site into it. These actions require permissions to create, and push code to future repositories, which is only available when granting access to
Here is a detailed list of all permissions we currently ask for:
|Repository Content (Code)||Write||Commit and push your initial site.|
|Metadata||Read||Default permission granted to all Github Apps.|
|Repository Administration||Read+Write||Create and delete repositories. We only delete github repositories upon user request, and only for repositories created by Stackbit projects.|
|Commit Statuses||Read+Write||Set "passing/failing" tags on commits in the GitHub UI if the build associated with them passed or failed.|
|Pull Request||Read+Write||Create pull requests for theme updates.|
|Repository Hooks||Read+Write||Setup webhooks to Netlify, some CMS, and Stackbit, to notify of new code, pull requests, and repository status.|
When are you adding support for [insert tool here]?
The site builder is designed to offer the ability to "test drive" Stackbit's tools and services. It can also be a useful tool for anyone new to the JAMstack and wishing to experiment with some of the popular tools in the ecosystem. Tthere are no plans on our current roadmap to expand the list of supported static site generators, CMS or deployment options. However, if you have a specific use case that you'd like to discuss, we're always open to hearing from our users. Email firstname.lastname@example.org
I updated my project name or domain at Netlify and now the links on my Stackbit dashboard don't work.
Once any DNS changes have propagated on Netlify's side, Stackbit will be notified of any changes to the domain or project name only once a build is triggered. If this has not yet occurred, you can trigger a build from either the Netlify or Stackbit dashboards to force the change to be picked up.
What is the Stackbit Control Center?
The control center is widget that provides 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. Every Stackbit project includes the control center automatically. 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.
That's cool, but I want more.
The control center are just some of the features that make up Stackbit, which also includes additional tools for inline content management and site management. You can learn more about Stackbit Live and even try a live demo on our home page.
How does the control center work?
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.
Can I allow additional site admins to view the control center?
Yes. Within the control center, click on the settings panel (i.e. the gear icon in the lower-right corner of the widget) and then choose "Copy Collaborator Link". Simply send that link to anyone that you would like to have access to the control panel. Please keep in mind that they will need to register with Stackbit before being able to access the control panel.
What headless CMS do custom themes support?
Uniform supports Contentful, Sanity, DatoCMS, Forestry and NetlifyCMS.
Do I still need to go into the CMS and define content schemas?
Ok but if I update my theme and change some models what happens then?
Ok, that's a tricky part. We do support non-destructive content-schema changes and are constantly improving our ability to fully handle them so you don't have to write annoying migration scripts.
What's the deal with this stackbit.yaml file?
It helps Stackbit understand how your theme expects to get its content and data. We provision whichever CMS you choose with the content model for your theme and when it's time to build we transform the content (did you know some CMS don't support default values, have unique naming conventions for variables, etc?) and prepare it for your theme and generator.