Storyblok Reviews: 4.5/5 — Highly Rated

The live editor makes content editor's lives happy as they can see a preview of their new page as they create or edit it in real time.

The official plugin with Gatsby is a bit outdated and doesn't work with the new Gatsby image API.

Easy for developers to create components for content editors to build new pages with. When a change is required on a page, no developer is required and the editor can do it themselves.

I love the visual editor as it is a great selling point when I was presenting this an option for the internal editors that will be using the tool. It is the only option I have found with such a feature.

I love using the GraphQL API although the documentation is not as clear as the REST API documentation. I would like to see direct integration with BitBucket for CI/CD rather than using a webhook that then relies on another service to integrate with BitBucket.

Allowing a dynamic website that can change without constant developer involvement. I built the site with the Nuxt framework and it was much easier than I initially thought to integrate Storyblok CMS.

I like that it is easy to use and customizable, and it has great content creation features that are very effective and easy to define and modify. It's packed with great visual ideas, and it's also effective when it comes to planning content. The user interface is excellent, as it is easy to find any function.

It is an easy to use tool but it needs to show more deatils in each of its functions and it does not offer drag and drop either and that is important because it will make the work much easier.

Managing content in a unique and efficient way, editing documents, managing web content, and editing images and text helps a lot more than you bargained for.

The fact that you can define your own components and connect them through the bridge to design pages visually is fantastic.

The tooling is a bit lacking. The javascript client is good, but we need official libraries for React/Next.js and Vue/Nuxt.js at least.

Traditional headless CMS lacks a way to design pages using components you have defined in your codebase. Storyblok let us create new pages by simply dragging and dropping some common components (things like heroes, CTAs, feature section, etc.) and then simply specify the values (props in our case as we're using React) to pass on to those components. And the best thing is that you get feedback in real time through the bridge preview.

Storybook's Visual Editor allows you to set up a 'bridge' between the CMS and your frontend so that you can preview (live !) your work et your changes... in the CMS editor ! Honestly, I have searched, tried, and re-tried others CMS and... Storyblok is the one that fits the most to my needs.

For internationalization, Storyblok offers the possibility to add several languages, but you can't change the default one, called 'default'. I would rather have the option to set an existing language as the default language than having a default one corresponding to nothing but 'default'. There are, however, workarounds and the Storyblok team keeps working on improvements.

Live preview of custom components is, to me, a must-have for my clients.

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.

Visual editor is excellent.It makes the website development easier and it's a game changer for content editing. Could easy integrate with custom plugins for various purpose. Awesome backup system with revisions. Great Image transformation API Easy to implement in every project due to the component based system. Easy API call both Rest and GraphQL

Some lack in internationalization. You need to use 3rd party app for handle different content per country. Unfortunately the tool plugins has some UI issues due to the small space reserved to them. Plugins development is not easy due to the poor documentation.

Storyblok drives the frontend development with components and bloks keeping CMS and frontend linked together. Visula editor is a great tool for content editor. Storyblok images service is very useful tool for image transformation.

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

You can achieve almost anything due to they way Storyblok gives you the data you need, collect that data in some flexible react framework (next.js) and you've got the foundations of a very smooth experience that you can tailor to those not interested in the code. Once the code pieces are put together the speed to market is rapid - components can be create and slotted into place very quickly and can be visually checked through whichever release process you decide to follow before it hits your production system - all thanks to that very clever visual UI. There is quite a bit of headscratching and effort that went into just understanding the best approach but once there it really is a flexible system that Storyblok can easily improve overtime; enough is there at the moment though to get going.

There are definately quite a few improvement points to made however, especially out the developer experience but there are work arounds, you just might need another backend tool to achieve them. - API limitation on resolving relations to a minimum of two levels - Documentation on best practice setup to achieve more complex tasks (i.e. this is how you would build a breadcrumb or on-page navigation) - Stories/templates that would inherit the limited component use from the parent Template or Story - API rate limt seems a bit low in some cases (100) - Webhooks trigger could be more granular, i.e. on a per story/template/folder level - Bulk edits to components/reusable content (i.e. I want this component to appear here on these pages) - Component re-naming checking (say you give a component a name that the API uses and you want to change it? Be great to see what pages thats impacted without having to write a bespoke tool to check and update/publish) - Another (test?) access level key would be useful in addition to draft/published (Test > UAT > Prod). - Image Service could do with a little improvements, its a bit hit and miss and sometimes a little slow. - Would be great to see an automated language translation option

When moving away from an old web system to a headless CMS, we want our speed to market improved with rapid response times that we could use with any web stack we decide on and any webstack we want to migrate to in the future.

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.

It is really easy to integrate with different JavaScript frameworks.

Not being able to import the types from the CMS for TypeScript.

It helps to manage, in a really easy way, the whole site content for both developers and writers.

The flexibility of creating stories with translations and references to other bloks or stories

Bugs that show up in v2 and rate/concurrency limits

Giving the ability to other teams of our product to customize the look and feel of it as well as handle the translations

Its simple and straightforward to use if you have experience using other CMS's such as Contentful or Prismic

They don't offer any templates to get you started with any of the codebases.

Provides a simple solution for a headless CMS for our clients who are looking for reliability and security for their web solutions

The user experience is very good, new editors can start working quickly without bigger introduction since the structure is really intuitive. Also in the backend there is a lot flexibility which allow us to reach different goal with minor effort.

I find really complex the dimensions and they don't work as I would expect from a very good tool as Storyblok. For multilingual webites it's important to have a clear process how to work with the languages and this is not the case.

We wanted to change to a headless CMS in order to improve the performance of our website with static pages, have much more flexibility introducing personalisation and A/B testing and also improve the editor experience.

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 like the UX of the app. It is clean and well organized which makes it very pleasant when you are using it. The preview functionality is great as well, I like how versatile it is.

Pulling images from Storyblok into gatsby-plugin-image isn't working for in the GraphQL query for fields of the "Blocks" type. This makes our team roll back to the old API.

It helps us to manage content on the website with good flexibility in component arrangement for a site-builder experience. It works fast and the responsiveness is great.

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.

I love how easy it is to get started with Storyblok as Headless CMS - the npm library "storyblok-generate-ts" makes it even easier to use the correct types while working with NextJS.

Because Storyblok is not a self hosted CMS, but is hosted by a third party in the cloud, it's harder to add custom functionality to it compared to other CMS solutions which are self hosted. (e.g. Statamic).

Storyblok really helped us speed up our development and deployment of new websites. Having previously used Wordpress for client websites, being able to skip the whole self hosting really is a life-saver. Also not having to worry about backups or data migration when moving servers, as this is not needed anymore.

StoryBlok is our go-to choice when we're working on projects with a JAMstack architecture. Devs are free to choose any technology stack when building their websites or applications. The killer feature of having a live preview truly helps content managers to visualize and plan things on the go. Besides all the above, you can enjoy a powerful versioning system to gain full control over iterations of the website, a strong community, and engaging support. StoryBlok is robust and allows us to build a CMS with a healthy amount of restraints. In other words – it helps the client to build consistent design experiences without breaking the patterns set by designers.

It's a bit too technical and would require a developer whenever you plan to ship something unique! So if you don't have a developer ready to maintain your StoryBlok CMS and implement completely new marketing and design initiatives – you better hire one.

Our biggest problem that Storyblok solves is the ability to edit content without breaking design guidelines. As a design studio, we care about design consistency, a lot! It's also easy to onboard new clients and ship out-of-the-box CMS solutions that are extremely flexible and configurable per each project.

As a developer, I do like the way of building pages. I just need to create my blocks, links them to the storybloks one and my collegas can just build pages with that !

French translation is sometimes not complete

It allows us to focus on building website & let my customers edit the content easily

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.

Storyblok helps us to move fast while managing our website. The CMS is very user-friendly. Colleagues with no CMS-experience are very quickly comfortable in the CMS and able to manage pages without any assistance. The facts that it's in the cloud, saves us resources on maintenance and updating software.

However the CMS is very user friendly, you sometimes have to click a lot to finish an action. You have to click through screen to screen to change some settings of a content block and that's sometimes annoying. Storyblok works 99% of the time, but exceptionally we experience some errors or slow servers. I would like to have that it's more close to 100% uptime for a system like Storyblok.

Our previous CMS was less user-friendly for editing pages and required a lot of maintenance like installing updates. These challenges are solved while using Storyblok.

The live preview feature of Storyblok is a game-changer for content management and boost productivity

Development is needed to get full potential of SB (live preview, customizable fields)

Provide a unique data source for our website

I like that there are infinite possibilities. Being able to create nested blocks is very powerful.

Previews are sometimes tricky to use. Default values don't always apply on existing content. It's a bit tricky to use sometimes.

Let marketing manage our website's content, while having full control on the code.

What I like about storyblok is the possibilities to modify my website and the ease of use. Storyblok allows me to upload blog posts in any language, upload new pages/offers or edit content already online. The preview function also allows me to see, before my customers, the changes made. This allows me to adjust what is not working. I can also properly organize my pages, layout, product sheet and easily find what I am looking for.

The Storyblok interface is a bit "old fashioned". I think the interface can be modernized with modules that are more "pretty" for users. Moreover, it's easy to get lost between items and sub-items on the same page when you want to modify elements

Storyblok allows me to modify my website, without having to hire a developer. I don't have the technical skills and our web developer recently left us. So I don't need anyone to drive sales anymore.

Storyblok is a good tool that allow you to add more blok in an easy way. Storyblok is a good cms that allows multiple combinations. We can do several things, whether it is articles, quotes or image blocks

Sometimes you have to add a new language in the datasources and you can't do it by yourself it's too bad because you have to contact the agency just for do that.

It is interesting to use storyblok for several reasons: 1. We are present in several countries and storyblok allows us to manage the content of our companies on the 4 countries via 1 single platform 2.Having only studied marketing, I don't have any development skills and thanks to storyblok I can take care of the website content easily. 3. Finally, Storyblok allows me to save time. Indeed, by focusing only on the content and not on the technical aspects to put them online.