You write code like you're used to
Your code with Stackbit looks almost the same as without.
The competition requires that you use their own components and APIs.
For developers
Headless Architecture Meet Visual Editing
Your Stack. Your components. No dependencies.
00:00 / 00:00
The modern web is great for developers, but less so for content teams.
Here’s how to make their work easier & faster - so you can keep working the way you like while doing less chores.
Easy to Adopt
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 ✅
The Stackbit difference
Stackbit fits your stack, rather than the other way around.
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 latency or points of failure in your live site, and no traffic-based billing.
Structured content, not blobs
Some tools support headless CMS by storing content as opaque blobs of data.
We use the full CMS schema - so permissions, validations and workflows work as they should.
HOW TO SET UP
Get started
Start from scratch
A fast-paced tour from site creation to customizing and publishing your site.
Add Stackbit to your site
See how simple it is to add Stackbit to an existing website.
