Headless CMS Playbook
  • Headless CMS Playbook | Rangle.io
  • Introduction
    • What is a headless CMS?
    • Benefits of a headless CMS
    • Headless architecture
  • Headless CMS tools
    • What to consider when choosing a headless CMS
    • Sanity: Most customizable
    • Contentful: Best for enterprise
    • Stackbit: Best visual editor
    • Strapi: Budget-friendly self-hosted
    • Honourable mentions
    • Choosing the best headless CMS for you
  • Authoring experience
    • Assessing capabilities and needs
    • Trade-offs
    • Best practices
    • Live preview
  • Content modelling
    • Understanding content models
    • Best practices for content modelling
    • Querying content
  • Static site generators
    • Comparing different build options
    • Popular static site generators
    • Component library
    • How to connect content data to front-end components
  • Conclusion
    • Key takeaways
    • Subscribe
    • More resources
  • Author acknowledgements
Powered by GitBook

Rangle.io

On this page
  • On-the-glass WYSIWYG editor
  • Self-hosting of CMS data
  • Framework agnostic

Was this helpful?

  1. Headless CMS tools

Stackbit: Best visual editor

PreviousContentful: Best for enterpriseNextStrapi: Budget-friendly self-hosted

Last updated 2 years ago

Was this helpful?

We recommend Stackbit to teams that need an on-the-glass visual editor. As a framework agnostic headless integrator, you can use Stackbit with any other headless CMS or self-host your CMS data.

On-the-glass WYSIWYG editor

provides a WYSIWYG editor that works with Sanity, Contentful, and any other CMS without slowing down your website. If you're looking for a self-hosted option with a stellar visual editor, we recommend using Stackbit with its own git-based CMS.

You can change content directly on-screen without navigating complex schemas on Stackbit.

Stackbit offers a user-friendly, intuitive interface where you can create and change content directly where you want it to be displayed.

Components don’t need to be written in any specific way or registered to use the on-the-glass editor, and the editor doesn't affect website performance as it isn’t part of the production code.

Self-hosting of CMS data

If you're looking for a self-hosted option with a stellar visual editor, we recommend using Stackbit with its own git-based CMS.

Organizations with sensitive data or strict security or compliance requirements may need to fully own and control their CMS data and infrastructure.

Framework agnostic

As a framework-agnostic headless integrator, Stackbit offers maximum flexibility and portability for your code and tech stack.

  • You can use their git-based CMS forever or move to any other CMS at any time.

  • You can stay on Hugo, Jekyll, or Gatsby and upgrade to Next.js, Vue, Nuxt, or anything else later.

  • Even if your tech stack changes, your content creation experience remains the same. For content authors, this means Stackbit could be the last platform they’ll need to learn.

This also makes Stackbit a powerful tool for website migrations. With Stackbit bridging the old and new CMSes, teams can migrate pieces of a platform while authors continue managing and editing content on Stackbit.

You can see content changes in real-time with live preview, but you can’t make changes on-the-glass. Shown here is Tina’s live preview as an example.
Stackbit