What is Stackbit?
Stackbit encompasses a variety of services that enable content management, live previews and site management. Currently these include the ability to edit content with live previews of the changes, add new or duplicate existing pages, share live previews of content changes and monitor site builds. Stackbit also supports teams via collaborator access and built-in workflow. If you'd like to see how these features work, you can try them now.
What CMS does Stackbit support?
The goal of Stackbit is to support any site, regardless of which headless CMS they choose. We currently support Contentful, Sanity, Forestry and Netlify CMS. If your company has a different set of requirements, we still encourage you to contact us 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. We currently support sites built with Gatsby, Next.js, Hugo and Jekyll. If your company has a different set of requirements, we still encourage you to contact us 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. We are currently optimized for deployments to Netlify but are capable of supporting a variety of other options. We encourage you to contact us and we're happy to explore how we can address your needs.
What do I need to do to support Stackbit?
Stackbit is designed to work on top of your existing tools without requiring any changes to your code. Stackbit does require access to your CMS and repository and can benefit from integration with your deployment solution.
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. We are currently looking into ways to improve and expand support for different tools. However, if you have a specific use case that you'd like to discuss, we're always open to hearing from our users. contact us
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 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.
Can I upgrade Sanity CMS in my local environment?
Yes, but if you run
sanity upgrade locally you also need to run
sanity build, and commit the resulting changes. There can exist a state where Sanity upgrades but the needed components in the code do not, resulting in the Studio not loading your site. Running
sanity build should solve this and is a best practice when modifying your Sanity site locally.