💾CMS
Connect to your existing CMS or the one that works best for you.
Last updated
Connect to your existing CMS or the one that works best for you.
Last updated
Webstudio is backend-agnostic, meaning it enables you to connect to any backend as long as it provides an HTTP API (see compatible CMSs and features for more info).
While some users may be used to seeing a CMS tab within their platform, Webstudio is different. It’s approached CMS by providing a flexible way to interact with third-party systems such as CMSs, CRMs, and databases.
Need help finding a CMS? Use the Headless CMS Finder.
The building blocks of Webstudio CMS are:
Dynamic pages – In their simplest form, they are essentially blog templates – one page that dynamically displays data depending on the URL viewed.
Resources – A way to fetch data from an API, whether it's a simple blog post or a complex data model.
Bindings – Enabling connecting or mapping the CMS data to Webstudio components. You can bind external data to any component and field within Webstudio, from rich text to meta titles.
3 minutes to get you acclimated with how CMS works in Webstudio.
Similar to a static page, the path includes dynamic parameters, like a post slug. This enables the page contents to change dynamically based on the requested page.
Adding parameters to a page path will automatically turn the page into a Dynamic Page.
The path can include dynamic parameters like :name, which could be made optional using :name?, or have a wildcard such as /* or /:name* to store the whole remaining part at the end of the URL.
The value of the parameter comes from whatever is in the URL. If the path is /post/:slug and somebody views /post/hello-world then hello-world is the value used in your Resource.
The Address Bar enables previewing Dynamic Pages in the editor by entering parameter value(s).
For the Dynamic Path /post/:slug, you would enter a slug value that exists in the CMS, such as hello-world.
The static part of the URL (in this case, /post/) is already in the Address Bar and should not be included when adding the test value.
Address Bar values are saved in the editor by:
Manually entering values
Navigating links that lead to the Dynamic Page, such as clicking on /post/hello-world
A Resource variable gets its value from a fetch request, allowing data from a remote system to be used within Webstudio.
In the context of Dynamic Pages, Resources are used to fetch specific information determined by the URL, or more specifically, the value of the parameter(s) in the URL.
For example, the Resource will dynamically fetch posts from the CMS whose slug value equals the slug being viewed. The query may look something like this posts(slug: system.params.slug), and when /post/hello-world is viewed, the query will translate to posts(slug: "hello-world") (i.e., “get posts where the slug value is “hello world”).
Dynamic pages may have multiple parameters, enabling the query to become even more dynamic. For example, in addition to :slug, you can also add :lang to fetch and display localized content.
If interacting with a GraphQL API, use the GraphQL resource.
At this point, the Resource Variable has the CMS Data, and now you need to bind or connect that data to the components and fields.
Binding data is done with the Expression Editor.
For example, go to a Header component > Settings > Text Content > and the “+” button. Within the Expression Editor, add the Resource Variable that contains the CMS data and the title value within it. This may look like CMS Data.title.
For more information, see the Expression Editor documentation.
Webstudio CMS supports any content management system (CMS) that provides an HTTP API. This feature enables users to use their existing CMS or the one that works best for them.
Below is a non-comprehensive list of CMSs, whether or not they provide an HTTP API (i.e., compatible with Webstudio), and the compatibility of specific CMS features. You can also use the Headless CMS Finder to compare and filter headless CMS options based on key features and pricing.
While we do our best to verify the supported features, we may make mistakes in our research.
While most CMS field types seamlessly map to Webstudio components (e.g., Plain Text → Heading), rich text may not, depending on how the CMS stores/delivers it.
Currently, Webstudio supports rich text if it's delivered in HTML or Markdown format. In the future, we will support rich text regardless of the format delivered by adding conversion libraries for each CMS's flavor of rich text. For example, we'll automatically convert AST to HTML. Refer to this issue for more information.
In the meantime, advanced users can set up a proxy on Cloudflare Workers to convert rich text to HTML. However, this is outside the scope of Webstudio's support.
Rich text in the form of HTML can be bound to the Content Embed Component, and Markdown can be bound to the Markdown Embed Component.
| CMS | Compatible | Rich text | Tutorial | Template | Known issues |
|---|---|---|---|---|---|
✅
✅ Must request HTML
✅
❌
✅
✅ Must use the CKEditor 5 integration and field as it outputs HTML. Not compatible with the default rich text field.
✅
✅ Using Markdown field
✅
✅
✅
✅
✅
✅
✅
✅
✅
✅ Need to create a field and hook that auto converts rich text from field A and saves HTML in field B (src)
✅
✅
✅
✅
✅
❌
✅
✅
✅
✅
✅
✅
✅
✅
