Improved Performance
A headless CMS eliminates the need to render the presentation layer when delivering content and reduces the amount of data that needs to be transferred, meaning faster load times for users.
Dato Webinar
UPCOMING WEBINAR
Maximize a headless setup with a visual in-context editor
Headless CMS like DatoCMS is a huge step forward separating code from content and allowing each to be updated separately. Adding Stackbit as an editing "head" allows marketers and business people to intuitively edit visually in-place, on top of any custom setup with a single config file and no added dependencies.
Why headless?
More Control
Developers have the flexibility to build applications with custom user experiences and use any technology they wish as long as they have access to the content.
Better Scalability
A headless CMS is designed to easily scale up or down as needed since the content is not dependent on the presentation layer. This makes it far easier to add new features and make changes without having to worry about compatibility issues.
Increased Flexibility
With a traditional CMS, the content is embedded within the presentation layer and tightly coupled with the user interface. This limits how much you can change or customize the application. But with a headless CMS, the content is decoupled from the presentation
Award winning enterprises trust Stackbit
Stackbit and DatoCMS for Developers
Stackbit fits your stack, rather than the other way around and connects seamlessly with DatoCMS for a complete headless setup.
You write code 
like you're used to
Your code with Stackbit looks almost the same as without. Contrast this to the competition - which requires that you use their own components and APIs in your code.
Your production site doesn't call us
Whether your website is static or dynamic - your production site does 
not need to call any Stackbit API. Meaning, no added points of failure or latency to your live site. No pageview-based billing.
Structured content, not blobs
Some tools support headless CMS 
by storing as opaque blobs of data. We use the content model of DatoCMS directly, so permissions, validations and workflows work as they should.
1. Run your website locally
Launch your site in development mode.
2. Add one config file
Add a stackbit.config.js file to your project.
Configure which content sources you use, and how content maps to site pages.
3. Launch the visual editor
Run stackbit dev in the terminal to launch the visual editor in local mode.
You're now already able to edit pages - with no code changes.
4. Unlock power features
Annotate your component with simple HTML data attributes.
This unlocks component-level visual selection, plus other power features: saving component to presets, styling controls, and more.
5. Create a cloud project for your content team
Create a cloud-based Stackbit project for your GitHub repository, and we'll run your code in an isolated container. Share with your content team.
First iteration done âś…
Stackbit for Marketing
& Content Ops
00:00 / 00:00
Materialize: superior governance, workflows, and speed after upgrading from WordPress
Materialize uses Stackbit to rapidly evolve their website and give marketers, lawyers, and HR professional independent control of their content.
Abodu: modern tech meets modern housing
Abodu, the future of modern housing in your backyard, leveraged Stackbit's visual experience platform to enable developer flexibility, speed, ease of use for marketing and content operations, all the while boosting SEO results.
Wellster: dev approved, marketer beloved
Wellster, an innovative next generation health provider, leveraged Stackbit's visual editing platform to improve developer efficiency while accelerating content operations and collaboration.