Renaming page URLs can be risky, especially if they have been previously available on your live site. To mitigate the risk in cases where changing the slug may be needed, we’ve introduced a warning in Stackbit for content editors to be made more aware of the risk.
Global access to 'Content' is now available in all workspaces independently from the data source(s) used.
.webp images are now fully supported in Stackbit and appear in the image dialog.
When using a list field where the individual items where of the enum type,
they would appear as dropdowns. You can now use a checkbox control for a
better editing experience.
With the Create from GitHub feature, you can bring any (valid) code repositories into Stackbit. This enables you to start a workspace locally, and only bring it into Stackbit when you're ready to add collaborators.
Whenever a content editor makes a change, everyone who's currently working on the same Stackbit workspace should immediately see this change. Up until now, installing packages and adding non-trivial code on both the server- and client-side was required in order for this to properly work.
It is now possible to add icons to each group specified in a model's fieldGroups property. We've provided a library of icons to streamline this process.
You'll now see see a visual indication when an object is referenced from multiple documents (pages or data objects). This also affects the modal shown when creating a new referenced object.
Organizations storing content for different teams or parts of a website (e.g. marketing and customer service) in a single content space can now split up the content across different Stackbit workspaces for better access control.
This is currently only available for Sanity.
Workspaces using Sanity as a content source now support fieldGroups and initial (default) values.
Share your contact info here, and book time with a member of the Stackbit team.
