Storyblok Reviews & Product Details

One of my favourite aspects is how lightweight everything feels. Page editors load relatively quickly (slow loading times can be one of the most painful aspects). I also like how the asset manager is laid out, it makes grouping images by page really simple. Another example of this: by grouping particular assets (such as brochures) it's incredibly quick to check which PDF assets are up-to-date.

I'd like there to be a way to add an ID to a specific block so it can be linked to directly. For example, if we want to anchor-link to a specific part of the page. There's a lot of basic functionality like this which seems to be missing. There's also a bug which is incredibly frustrating where whatever you type into the text field starts writing out backwards, you have to click back into the text field and delete the backward text to continue.

On our previous CMS, adding new pages was incredibly difficult and could only be achieved with external developers. With Storyblok, very little work has to be sent to external developers, we can create site-wide blocks and copy and paste them to new pages painlessly.

Seeing a page change as you make changes, being able to copy and duplicate components and pages within seconds. These features really do make creating your website pages super quick and easy. The UI too is very easy to use and requires minimum training, in fact in most cases it is simple enough to work things out without any support.

be able to undo deletions by mistake, this might be something we havent yet discovered how to do but if you accidently delete a component or page there doesnt appear to be an 'undo' type feature that would just undo that one change. I think another small thing is as there is no formal training, it has taken us longer to discover some pretty useful features we may have discovered sooner if some more indepth training was offered.

For sure the ability to scale up and publish new pages, new templates and new content without developer input with the ability for the user to view the page as they create it is a real benefit as this really does cut down the time to market of producing new and valuable content.

Storyblok makes it easy to quickly build sites with completely custom UIs, and allows you to define customisation at whatever level of granularity you want. It is very cost effective relative to alternatives such as Contentful and is better geared towards design rather than data entry (as Sanity is, for example).

Internationalisation is not trivial and the APIs for handling multi-lingual content aren't ideal. The UI is also not really designed with translation in mind and it is hard to do an external round trip as well.

Storyblok allows us to have a completely custom static site, built in house, but that is easy for marketing to make changes to. We've designed our own content structure of sections and blocks to allow them a lot of flexibility while still providing a look that feels like it has been coded from scratch.

Our team has used Storyblok as a headless CMS solution for more than 2 years now. After multiple projects, I find that the complexity of achieving certain features reduced dramatically – when compared to 2 years ago. Looking back to when we first adopted Storyblok on a regular basis, I've seen the product improve both in editor and development experience — visual editor, bridge and asset manager. Based on this I believe Storyblok's strong point is that their team listens to developer and customer feedback and uses that to continuously improve their product. On a similar note, it's easy to get direct access to their development team when you contact support. I am especially happy with the Image service and the GraphQL API (although this one isn't as clearly documented as its REST counterpart).

Creating user roles on spaces and managing granular permission for each role leaves a lot to be desired right now. I'm also not a fan of their plugin/custom app development ecosystem forcing developers to use NuxtJS/Vue – although it's not as problematic now that they also provide their component library as a package. Table fields could benefit from allowing rich text editors on cells instead of plain text fields. Their CLI for the management API also doesn't parallelize requests. Likely there's a reason behind it, but we found it slower than desirable for our needs to upload assets in bulk.

We're using Storyblok as the content layer for multiple applications, mainly corporate websites. For applications belonging to the same organization, we found it trivial to "containerize" all application configurations for each affiliate/branch using datasources.

Thea ease of use and the possibilities to create custom components that can be modified by content creators without the help of a developer

The folder structure can leave a lot to desire if you have a lot of components or pages created within the framework

The use of development time to actually change content on a website; The people that are responsible for their content can do this without a developer's help

The drag and drop feature is awesome to use components with

The redirect configure tool can be slow sometimes but that's just about it

Quick website updates that our development team used to have to manage so it's saved a lot of time for our business

A great headless CMS with a really good visual editor / live preview. This means that even staff without a technical background can easily maintain content. Good expandability through own plugins.

There is currently no market place for plugins. Integrating product data from your own e-commerce system could be even easier.

Storyblok is the CMS for our Webapp

Its real-time visual editor makes content creation very easy. It works with almost all different languages and supports all kinds of projects. The headless feature helps to maximize efficiency and thus faster content creation.

There is nothing to dislike about this intuitive headless CMS. It has got all the requisite features for a perfect headless CMS that helps to speed up the content process.

We are primarily using it for the content management of our website to make changes to our website with ease and without minimal technical know-how. The whole process is quite simple and easy and helps us boost our content creation process.

An easy-to-use interface for editors to manage content autonomously. Updating content with Storyblok is a lot faster with cross-platform delivery without additional work

For the non-engineer it might be less flexible. Doesn't take a lot of time to learn though which is probably a good thing.

Switching developer focus from maintaining online properties to prototyping new ideas. Easily reuse content across platforms. Frees us up from doing manual updates

The developer support and documentation are phenomenal. Storyblok offers the ability to hit the ground running with support for all your favorite frameworks.

The UI could use a little polish in comparison to sho gun. Also, it would be nice to improve the way you parse the component tree in the UI, and it can be challenging to move up and down the tree.

Our Marketing team was moving faster than the development team could keep up. Storyblok was the solution by allowing us to build a component drive solution so that the marketing team could build as fast as they wanted.

Easily creating components and implementing it with your React framework. Easy to learn, easy to extend and make more difficult applications. Also, easy to learn it to the content editors.

The making of plugins is only in Vue, which I do not prefer. Making it able to choose between different libraries/frameworks would improve it. React would be great.

Not using hard-to-use SaaS for CMS anymore and have more grip on your data structure. This results in making more in less time! Also, not working with Wordpress anymore.

Very user friendly and easy to work with tool that I use almost daily. Here even an experienced user can learn and progress very quickly. Implementation was a very smooth process as well.

There a few functionalities that it still lacks, which prevent experienced user to get more creative, i.e. adding HTML assets.

Managing a constantly changing environment of our website.

I am using Storyblok as an employee to build Landingpages for my company. It was super easy to get used to the work environment. The interface is easy to understand and navigate.

Copying text from my word document can screw up the formatting sometimes. This can be a bit annoying. It is also hard to find the right/most relevant page when using the search.

Storyblok helps us to quickly create and change landing pages, an aspect that is important in a fast moving company.

Simple modern UI, stories and blocks are easy to understand and implement. Customer support responds in less than 48h Integration with the Javascript ecosystem is straightforward

No environment isonation, no easy way of migrating between spaces either These are the only features I miss, but theya are planned to be there next year.

The editor team can easily edit our App's content, and we can set up rules to verify it before it goes to production.

i work on creating and publishing articles, sometimes i do website maintenance and i do all of these easily without any knowledge of coding .. just storyblok. great job guys

sometimes i get logged out unnecessarily, although i understand this is for security reasons

it provides ease and makes my writing and publishing faster compared to other mediums

StoryBlok previews are great for allowing content editors to see what their pages are going to look like live in the browser. We have easily integrated it into our applications using the GraphQL endpoint. Also a big fan of the image processing power for use n the front end of our applications.

The GraphQL response can sometimes feel a little bloated and clunky but that could be more to do with the way we have structured our data rather than how it is processed by StoryBlok

StoryBlok is creating a really user friendly platform for our content editors to add pages and components to pages. The UI is slick and intuitive and the headless CMS allows us to use whatever frontend framework we wish to so that we can deliver super fast applications to the browser.

The visual editor is a huge advantage in terms of usability. Especially for pure content creator teams who can directly see what their page will look like. This also enables fast review processes, as everything can be seen at first glance. Also, the onboarding of new users is super easy with the visual editor, because users can directly see how modules and components will look like, interact with each other or how they can be changed by simply trying them out. In general, I have also experienced great and very quick responding customer support.

The permission management does not yet cover all our needs or is lacking some basic predefined roles such as translators that can only access and change the content within every block but can't change the structure. You can set up the roles yourself but it is not as intuitive to set up as expected.

Storyblok solves the usability problem that many CMS bring with them and at the same time does not limit the flexibility of the setup. It allows not only content teams to use it in a user-friendly way, but also developers to define the set of components and modules.

Storyblok is easy to use, easy to setup intuitive headless CMS. The available documentation gets you up to speed in no time. The app directory helps you connect to different services if needed. The fee community edition is a great solution for smaller businesses and even personal projects.

Major drawback for clients is the pricing model. The lower tears a very competitive compared to others in the market. If you want to set up some sort of OTAP or perhaps just Test and Production, you'll need to go for the enterprise tear.

Providing SaaS headless CMS. I don't need to worry about any further updates and security issues. The Visual Editor is easy to understand for marketeers, so the content editing shouldn't be an issue.

I really like the nice User Interface connected with the very clear User Experience. You can find all needed features very quickly in the web app and they are very easy to use. Also the integration into web apps like next.js is very easily done and intuitive.

Some downpoints are maybe the limitations when using assets (limited file sizes, no easy option to provide assets via custom domain..) However, I am aware that this is depending on which plan you are using.

Being able to manage the content of web pages easily and in an intuitive user interface and providing this data to the web application.

What I like about Storyblok is its flexibility and ease of use. The fact that it is a headless CMS allows developers to design a flexible content architecture that can be adapted to different platforms and channels. Content teams also appreciate the ease of use of the user interface and the ability to create content collaboratively.

I've noticed that the content management interface can be slow or cluttered, especially when there is a lot of content to manage. Overall, these limitations and issues are relatively minor compared to the benefits and features offered by Storyblok

Storyblok solves several common problems in online content management, such as the need to create and manage content for multiple channels and platforms, the need to create multilingual websites and the need to work collaboratively with content teams. Storyblok makes it easy to create and manage multilingual websites with its translation management features.