Uniform Themes

What headless CMS does Uniform support?

Uniform is starting with support for Contentful, DatoCMS, Forestry & NetlifyCMS with more CMS coming soon.

What is the plural of CMS?


Do I still need to go into the CMS and define content schemas?

No more! Define a Uniform content model once in the stackbit.yaml file and Stackbit maps your content to every CMS. So you now actually have time to pick up a new hobby like growing Bonsais, playing Rocket League or start an Etsy shop.

Ok but if I update my theme and change some models what happens then?

Ok you got us, that's a tricky area but 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.

Can me, my customers and/or my company really create CMS-powered websites from my themes with a single click?

You likely know Amazon has a patent on that single click, or maybe it's only for eCommerce? At any rate we're more like 2-3 clicks but constantly looking for ways to reduce those clicks.

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.

I don't like YAML files why didn't you go with JSON/TOML/XML/CFG/Hexdump?

Our almanac said we should use YAML so we didn't ask any questions.

I love AmazingCoolFunkyCMS why don't you support it?

Let's do this! If there's a particular CMS you're looking to use please drop us a line.


What static site generators can Unibit convert to?

Unibit is starting with support for converting to Jekyll, Hugo & Gatsby with more SSGs coming soon.

What's the difference between Unibit and [enter name of static site generator]?

Unibit is a superset of existing static site generators, it was initially built as an internal tool for developing Stackbit starter themes and when we realized how powerful it was we decided to make the spec and site generator open source.

What's the schedule for open sourcing?

We have released the Unibit CLI as a public repo which contains minified code because we're still doing some refactoring. We plan to release the clean code sometime late July 2019.

When should I use Unibit?

Unibit is a great fit for when you want to build a theme once and have it be available for people to use in a variety of different SSGs. A classic example would be you are a theme developer and want to sell Hugo/Jekyll/Gatsby/etc versions of the same theme - with Unibit you could write that theme just once.

When shouldn't I use Unibit?

Unibit is helpful when you want to code once and have your theme transpile to multiple different target static site generators. If you're set on a specific stack then skip Unibit and go directly to Uniform to easily integrate any theme with modern headless CMS.

Why doesn't Unibit have feature X?

Unibit is still a pretty young project so some things will naturally be missing. If you think a certain feature could be useful please drop us a line.

When are you adding [enter name of static site generator] as a conversion target?

We're working on adding conversion targets all the time. If there's a particular SSG you're looking for please drop us a line.


Is Stackbit FREE?

Stackbit is currently in beta and completely free. Once we go out of beta we plan to keep a large chunk of the functionality free to enable developers to use Stackbit for personal projects, learning new technologies, etc. We plan to introduce an affordable SaaS pricing tier for people who build websites for a living, agencies, etc.

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 All repositories.

Here is a detailed list of all permissions we currently ask for:

Repository Content (Code)WriteCommit and push your initial site.
MetadataReadDefault permission granted to all Github Apps.
Repository AdministrationRead+WriteCreate and delete repositories. We only delete github repositories upon user request, and only for repositories created by Stackbit projects.
Commit StatusesRead+WriteSet "passing/failing" tags on commits in the GitHub UI if the build associated with them passed or failed.
Pull RequestRead+WriteCreate pull requests for theme updates.
Repository HooksRead+WriteSetup webhooks to Netlify, some CMS, and Stackbit, to notify of new code, pull requests, and repository status.