Stackbit can convert a Jamstack theme located in a git repository into a functioning Jamstack site.

When a user imports a Jamstack theme built with one of the existing static site generators (SSG), Stackbit Site Builder uses the configuration defined in stackbit.yaml to create and configure a new Jamstack site. The site creation process involves creating and provisioning a new GitHub repository, a new headless-CMS project, and a new serverless deployment platform project such as Netlify.

Stackbit Site Builder Diagram

For example, suppose your theme is pre-configured to work with an API-based headless-CMS, such as Contentful or Sanity. In that case, Stackbit Site Builder will use the import object defined in stackbit.yaml to create a space in Contentful, or a project in Sanity, and provision it with the content schema and the initial content stored in the special export file.

If your theme is pre-configured to work with a file-based headless-CMS, such as NetlifyCMS or Forestry, Stackbit Site Builder will create and configure projects within Netlify or Forestry.

In case your theme is not configured to work with any CMS, but it stores its content in flat content files such as markdown, json, yaml. And you want sites created from your theme to work with Stackbit's on-page editor. You can provide the website's content models in stackbit.yaml using the Models and the Fields. Read our conceptual guide about Content Models to learn more.

When you import a theme into Stackbit, it will validate the format of your stackbit.yaml and will validate the content schema against the content files. You can use Stackbit CLI to validate your stackbit.yaml locally.

After Stackbit creates a new site, the stackbit.yaml continues to serve Stackbit Studio.