There can be stumbling blocks or "gotchas" you may encounter when developing your CMS-connected site. Part of this is due to the decoupled nature of the architecture. Below we share some best practices when working with the Jamstack and a headless CMS.
What's the Difference Between API-based and Git-based Headless CMS?
Content Modeling
- Make Fast, Versatile Jamstack Themes with Page Builder Components
- How to Add a New Tailwind Component to Your Site On Stackbit
- Sectioning an Existing Theme For Components
Best Practices for API-based CMS
- Using Headless CMS Validation Tools To Clean Data For the SSG
- How to Prevent Run-time Errors When Pulling Content From a Headless CMS
- Ecosystem Tools for Easy Consumption of Content
Best Practices for Git-Based CMS
- Making Content Scalable and Easy to Edit with Content References
- Managing Content Relationships in Netlify CMS
- Managing Content Relationships in the Forestry CMS
Understanding Content Slugs
- Best Slug Practices When Using the Jamstack with a Headless CMS
- Using Content Slugs in Popular Static Site Generators
- Managing Content Slugs in Netlify CMS
- Managing Content Slugs in Contentful
- Managing Content Slugs in Sanity
Gatsby How-to Guides
Gatsby is a powerful tool for building Jamstack site using JavaScript and React. Stackbit makes it even easier to build Gatsby sites in minutes that are connected to a CMS and have features like inline editing, live previewing and collaboration tools. Still, there are some common improvements users want to add to their sites like: