Let your users edit websites as they browse it.
The visual composer gives you a preview of the changes you make to your website, even before those changes go live.
Content Types with Blocks
Nestable content blocks make content management easy, even within complex layouts.
You may already create components like teasers, grids or feature sections. Content blocks allow the developer to reuse those components elsewhere, refilling them with new content each time if necessary.
Custom Field Types
Extend the editing interface with your own plugins.
Storyblok has with a robust and flexible plugin system to give you the power to extend the editor with custom fields like a color picker or a google maps location selector.
Choose field level translation or multiple content trees.
Delivering content internationally? With Storyblok you can define your own content localization strategy to serve multiple countries and languages.
Set-up your own content staging workflow.
To run a reliable production environment it is crucial to define different stages to test your content before it goes live.
That’s why Storyblok allows you to define multiple branches of your content and deploy only approved changes.
Track changes and restore to any point in time
Accidents happen. Storyblok let’s you always rollback changes with an unlimited version history and deleted content items can be restored from the trash bin.
Transform your images on the fly
Storyblok transforms, optimizes, and caches your images in a CDN for fast websites and apps.
Fine graded access control
Manage access down to the field level
Create roles and ACLs to enable safe publishing, while preventing unauthorized changes.
Add additional security with backups
Configure manual or automatic daily backups of your content and component definitions to your personal Amazon AWS S3 bucket.
Only use the features you need
With the app store you can selectively add features to Storyblok. This keeps the UI clean and clear.
Features that we are gathering more feedback on.
Multilanguage Admin Interface
This should replace all Strings in the Storyblok Admin interface with a specific key and allow the community to translate those keys for a specific language. A user of the Storyblok admin interface should be able to choose a language in their profile which will be used in all spaces to replace the default Storyblok information with a translated version. Custom content fields and their displayed labels should be translatable and only default to the current Display Name. Besides the textual changes it should also provide RTL support for specific languages.
Customizable List Views
With customizable list-views it should be able to define which top level fields of your content types should be shown on the overviews in your space. This should allow a custom set of fields to be displayed in the overview of Content so those fields and their information will be immediately visible to the editors.
GEO Location Filter and native Fieldtype
Idea is to provide a filter where you can search items near a geological point like, eg. geo-search. The fieldtype should provide a map with an address search field to set a pointer to a specific latitude and longitude.
Features planned and in development.
Component Groups / TagsReleased
With component groups and tags you will be able to add a virtual structure to your list of components. This will make the organization within components easier. Besides the better organization of components we consider adding a specific group or tag as whitelist to the blocks field type, so one would not need to update block fields if a new component is introduced and whitelist is in place.
The Storyblok Workflow provides a standard four eye content approval workflow. The name “four eye” comes from the fact that first an editor will create the content and then a publisher will approve the content.
In the event of a rejection, the workflow will move into a revision cycle where comments can be passed to the editor about reasons for rejection.
Configurable Markdown EditorQ3 2019
Idea is to provide configuration options in the schema definition of the “Markdown” field type to hide specific formatting options. This is especially useful for the Rich-Text mode.