Storyblok Reviews: 4.5/5 — Highly Rated

I love how easy it is to define data structures and the fact that it has all the types you could ever want. I've used WordPress as a headless CMS before learning about Storyblok and just to enable the API it was a mess. The Storyblok API is really easy to work with. Clients love how easy it is to use the editor and we can create some really complex setups for them.

When I first started working with it, every time I made a change to a piece of content it wasn't updating instantly in the API but this seems to be resolved with V2.

We use Storyblok for almost all new projects. It's great both for us developers as we can get a model setup in no time and for the clients as they get to edit their content in a clean UI with full flexibility.

Fast and simple CMS. Good translation features with export/import as json. Fast live preview of all content changes. Good API documentation for custom integrations.

All Storybloks good features and performance comes with a cost! It can be expensive for a smaller company, but it's nothing compared to the time you would have spent on a worse and slower cms. Custom add-ons also cost development hours for a non-technical person.

How many have spent too much time in a content management system? With this fast and simple CMS, there is nothing that can stop you. With 7 languages on a website, there is nothing other than field translation that facilitates my work. Combine field translation with import/export of the translations and you get more time for other important work stuff than spending time in the CMS. No third-party plugins makes bad security.

I found the visual editor and the overall UI/UX super easy to navigate and work with to populate content into the CMS compared to a lot of other offerings on the market.

My only dislike is, that some of the resources like the next.js starters or the video tutorials are out of date. All the resources need to be regularly updated.

I come from a WordPress background, where I have to worry about security updates, hosting etc. Storyblok takes care of all of that so I can just focus on developing a front-end.

Easy Integration and the Visual Editor. ..

No pricing mod for small companys who wants premium Features.

It gives us ine of the best visual Editors.

The flexibility of the components and the reactivity of the whole interface is very practical

The features can be complex sometimes for early users or final customer.

The need to have custom field for every type of content associated to a complex e-commerce product page.

The thing I like best about Storyblok is without a doubt its visual editor. Not only has it been revamped and re-imagined in V2, but it's intuitive and content-editor friendly. It's the "drag & drop" experience we've all been waiting for. And to top it off, they have an amazing community to boot.

The only thing I dislike about Storyblok is when compared to CMS's like Contentful, it isn't as "battle-tested" as one would say. In turn, it is prone to some hard-to-debug issues (even with the visual editor) with not as many resources to help you get unblocked. The app store/marketplace is also lacking but the same can be said for a variety of CMS's out there.

For my agency, we're looking to build enriching experiences for our clients that not only let them to make compelling visual content but empower them to do so at ease.

Storybloks Visual Editor is a game changer for Marketeers while developers enjoy the power and flexibility of the headless approach. You see in every bit of the product that the product team behind Storyblok understands what's important for a new generation CMS.

Having a lively ecosystem around your product is important. Storyblok is a young product and the ecosystem is growing fast but it is not yet where others are in terms of ootb connections to other tools and services.

The easy to use and is intuitive UI of Storyblok make customers of us work fluently with the CMs while many of them hired an agency to put their Content in the CMs before they moved to Storyblok. Our development team enjoys the power of flexibility. No fixed templating language built in like for traditional CMS. Storyblok plays well with any modern Frontend technology.

This software makes it easy to manage website content. People with little development experience can use Storyblok to manage their websites. As a front-end developer, I think it is an excellent program. It is well designed to make inserting new content extremely simple. From the side of my clients, I must say that they like the interface. I like this because I don't have to help them just get used to it.

At startup, Storyblik does not load the user editors. However, this is solved by teaching them what your working tools are. Anyway, it's a minor feature that does not affect the performance or user experience.

I use Storyblok to develop and manage the most simple projects under my care. The Real-Time Visual Editor feature helps me to preview and improve the design as I write the code. It is a perfect program for scaling up old websites that are already published and need updating. Generally, it is perfect for any type of project and standardizes the work methodology. The development times of this kind of projects have decreased significantly.

The ease of development with Storyblok is incredible. The real-time editor is really helpful. I can easily see the changes I make to the code without compiling it. It is an exciting feature of the new work approach. The existence of plugins extends the program beyond what I would have expected. But, best of all is the ability to create and install my own plugins.

I have not had any dislike of Storyblok. Like any CMS, it has a learning curve, but the reality is that it is effortless in this case. So, new users can adopt it at any time.

As a programmer, I like anything that makes my job as easy as possible. As a result, projects are developed very quickly and comfortably from the start. I have been able to develop simple client jobs in much less time. In addition to shortening my programming periods, I have been able to take on new projects and improve the company's profit margins. Creating this work methodology has been one of the most significant improvements in our company.

Storyblok is instant Wysiwyg while typing. Work with multiple people in so-called releases or use them by yourself for future releases.

Personally, I would use more distinctive colors or symbols to have a better overview of the status of the pages.

As a webmaster I need to find and add/adjust lots of files as quick as possible. Because of Storybloks clear overview and speed I can do just that!

Intuitive Webfront to edit data, easy to set up

No real Data view with tables for datamanagement, building components can get slightly cionfusing

Enabling my customers to edit pages that are build on modern jam stack

Easy to get started with, great integration, live previews, and content editors no longer have to fear a headless CMS.

Rich Text (custom Components) within Nuxt 3 is not yet fully supported

It combines the benefits of a Headless CMS with an easy to use UI. Our Content Editors love working with it.

We love that Storyblok works with all frameworks. Also, Storyblok is endlessly extendable - that makes difference

Overall Storyblok is an awesome product and we love working with them

Storyblok helps us to work on large-scale and Enterprise projects

Having originally used Storyblok out of pure curiosity, I quickly found that it somehow incorporated all the best features and functionality from some of my favoured CMS platforms. As a headless CMS out of the box, I love that there's no barrier to entry here - it's well documented, easy to pick up and you know what you're getting in to immediately.

So far, I haven't really found anything. I can see a need for some experimentation every now and again, especially for anybody who's newer to composable architecture or anybody who hasn't used such a modular CMS previously.

For any small brands or individuals that I speak to - the Community tier makes "best in breed" super accessible to a massive range of users and I recommend it with gusto! I'm working with more and more large brands who are making use of Storyblok to very quickly build and deploy new CMS platforms and are thrilled to be able to remove friction for both business teams and developers alike.

The atomic design approach, a user-friendly interface. Preview mode, Real-time changing without saving the modification.

Sometimes buggy preview editor. Not many ressources for Next.js

Easy development, re-usable component. Fastest development and easy to modify for a non-technical user.

A Headless CMS with a visual editor experience for your custom built components.

Storyblok does not yet offer a module preview. When you have a large amount of useable modules you are not able to remember all of them. (How the look/feel). This of course is fixed in Storyblok V2 with "Module Preview Images".

With Storyblok it is possible to quickly create/model a JSON Storage/Content and provide it seamless to every technology either frontend or backend applications.

It’s the full package that works so well for me, Storyblok feels like a well thought out and complete product. As a developer I love how it easily allows me to build complex structured and related data but for a content editor they can use a visual editor and see their changes quickly and easily. The API is easy to work with and outputs JSON so can be consumed and transformed as needed using whatever technology stack you’re comfortable with - Vue, React, Laravel etc. Headless CMS’s clearly are the future, decoupling the content from the frontend makes so much sense. So often a website suffers because the frontend is so tightly coupled to the content management system that upgrading it means upgrading everything. With a headless CMS you can freely replace the frontend whilst retaining the existing backend or push the same content to multiple channels. The team is fantastic too, iterating and improving the product with new features and always friendly when offering support.

I can’t think of any major issues. There was a bit of a learning curve about how to best consume the API and structure content but nothing more complicated that any other CMS.

I’ve used and made a lot of content management systems over the years and they’re all suffered from similar problems. They either lack the flexibility to create the desired content structure, are very cumbersome to use, become ‘plugin hell’ with a mishmash of varied GUIs and duplicated functionality or are very hard to update. Storyblok solves all other these issues. You build any schema you want for your data using a range of fields such as images, richtext, relationship links, or create your own VueJS based plugins. The interface is very clean and simple to use for editors - much of it takes place in the visual editor that allows content editors to see changes swiftly. As it outputs JSON you are free to totally change the website when updating without the usual migration headaches.

Storyblok makes it super easy to move from a static template to a dynamic website. The integration with our existing Laravel system was relatively easy thanks to detailed guides, and the excellent support was able to answer our open questions quickly.

The interface of Storyblok V1 is a bit tricky for some of our customers, but the V2 promises a significant improvement here. Resolving relations with the "resolve relations" function can also be a bit complicated with intricate components, but eventually, we were able to solve all questions with the help of the storyblok support.

We already had an existing website which we developed with the backend framework Laravel. However, this was not practical for regularly updating content. The integration with Storyblok to create dynamic content was pretty seamless. The loading times have improved a lot with Storyblok content delivery. The image service is also brilliant, you hardly have to worry about the size and format of the images you use.

Storyblok's visual editor is revolutionary. Never it has been easier for developers and content editors to use a CMS.

Storyblok works well. However, the documentation could be better sometimes. I know Storyblok is working to improve this.

Creating a website + CMS that works for both developers and content editors.

The product is super easy to use, and the simplicity of connecting your own components to the platform is incredible. You can give the marketing / management / design teams super powers to create and manage pages.

The approval flow needs rework, it takes a while to understand how it works.

We used them for two things: - Manage a bank application in multiple languages - Launch several landing pages (also in multiple languages) Storyblok solved our issue with the management team that wanted to have full control over the content and also the page.

The editor's user experience with Storyblok is flawless. Integration was easy for our developers to achieve.

Nothing in particular, some minor features are missing, like rich links (allowing for javascript attributes).

Help create SEO-relevant content that can be integrated into our eCommerce store. The headless, API-based approach makes for reusable content and easy integration.

it has a large FAQ section and the high customizability is a big pro

none so far that I have explored in my interactions

Using it for Nuxtjs frontend in my work and personal projects.

It's a no-nonsense headless cms with a great delivery API. Also it supports the types of nested content that supports structured content very well (like for producing website structure and slugs deep slugs).

The tooling is extensive with SDKs for several frontend frameworks. But, at the time of writing some of them could require better documentation and structure.

Using Storyblok as CMS for several websites and one content-based app.

It was very easy to implement Storyblok in our Nuxt application. And also very easy to create content with the visual editor. Everyone is satisfied with the new CMS

If i have to mention one thing, it would be that it isn't possible at the moment to filter published/unpublished stories. Which makes it hard to check where we have unpublished content.

Before Storyblok we had our content in the code, so we needed software developers to update the content of the page. With storyblok it is much easier. The development team can concentrate on the big things.

Storyblok makes it easier than ever to manage website content. All of my clients have mentioned how easy it is for them to go in and manage their website content. From a developer standpoint, Storyblok is excellent. They make it extremely simple to create new content blocks that can easily be implemented.

I don't really have anything negative to say about Storyblok. The only thing I would ask from the Storyblok team is to add built-in Typescript type definition generation. In the meantime, I created a npm package that does just that: https://www.npmjs.com/package/@brbndigital/storyblok

Being able to set up a CMS in a matter of minutes and have it integrated with whatever project I'm working on quickly is a massive time saver. Not only does it save me time in my development cycle, but it provides an easy-to-use interface to my clients so they can manage their own content without too much hand holding.

The implementation is easy and useful. The flexibility is also really good and the support helped us out multiple times.

Better comparison tools between different spaces so you can easily upgrade them.

We developed our own PWA Odoo application and this is a great asset to the stack. Multiple webshops are being made more flexible thanks to this feature.

The visual editor combines the atomic component approach with the ability to directly see the result of your work. That way it's easy to make sure your content behaves like intended.

Sometimes it's hard to wrap your head around the fact that storyblok is *only* a content hosting platform, if you come from an old CMS that are mostly all in one solutions for content, forms, business logic and whatever else you need.

While developing very specialized tools for customers, they often want some kind of content function. Instead of re-inventing the wheel, we can just outsource that part to storyblok and concentrate on the business logic.

It's very easy for anyone regardless of tech background to make updates and changes to the site.

I don't have dislikes of Storyblok based on my role in using it.

The marketing team owns the website and has varying degrees of CMS knowledge. Storyblok makes it much easier to divide the work among many since it's so user-friendly and straightforward for any skillset.

The visual editing experience is great. My coworkers in marketing who have been using it for the past 6 months have had only good things to say about it. Its so easy for developers to extend and for marketers to use.

The permissions are very granular but could be even more so! I'd like to have more control over exclusions of different content types.

Allowing marketers to create content without developers, and quickly see their work before it goes live. It has improved our publishing experience for everyone.

Storyblok provides a complete solution when it comes to a content management system and much more. It comes in with a visual editor which enables content creators to create and update their website's look feel as well without any help from developers. As its core offering, Storyblok provides a robust infra and an array of functionalities ranging from managing content (both website pages and blogs), tags, asset management, and even component creation. Using components, one can create reusable website widgets and use them on the fly as and when needed. Management of components is also fairly easy as is the whole user experience of the product. For the developer side, they provide APIs so that, if needed, Storyblok can also be used as only a CMS while one can have their front-end design. Overall it is a very usable and impressive product.

Nothing major. The app directory is still to grow I think but that will happen with time as adoption increases for the product as newer use cases would be identified with an ever-increasing user base.

We were exploring CMSs that provide APIs and also supports reusable components so that we can use our own user interface while do not invest in developing a CMS in-house.