We're introducing default project roles for users in Stackbit. With this change, it is now possible to give access to a cross-functional team to a project where every team member will just get added with their default project role as opposed to everyone in the same team having to be added with the same role.
Stackbit has first-class support for two-way syncing content between DatoCMS and the Stackbit visual editor. Enhancements in this release include:
Publish per page and per object
Documentation examples
This change introduces the ability of automatically giving organization members access as admins and any default project role according to the groups defined in the company's Identity Provider of choice (e.g. Okta, Ping Identity, Auth0, etc.).
Use Bynder to manage, transform, and deliver assets.
The new onContentCreate method makes it possible to set up Stackbit to create related and nested content when a new document is created. A common example is to use this field for dynamic default values — content created based on content input by the user.
This change introduces the ability of filtering by referenced objects. For example, find all posts with author 'John Doe', or find all posts with tags 'sports' and 'music'.
Custom asset sources provide a way for you to flexibly bring your own asset behavior without the need of a direct integration.
Bring custom behavior and content transformations by hooking into Stackbit's document lifecycle methods.
We provide the most unobtrusive solution in our domain, but annotating your components at scale is a notable challenge. Here’s a scalable solution.
Improvements in the container logging include visibility on container stages and commands it's running.
Share your contact info here, and book time with a member of the Stackbit team.
