Storyblok Reviews: 4.5/5 — Highly Rated

Great Pricing! It is actually affordable for small businesses Components are generally quick and easy to put together Compiling content is simple and intuitive for the most part but not very reusable (the biggest issue for me)

Reusable components in content desperately need to be implemented, and the current nestable/global types that need to be added to related key through API sucks. Currently I need to manually copy content across multiple pages, which is a nightmare when it needs to be updated... Presets are cool, but only when creating; why can't I update the preset to all instances where I used that preset??? API documentation could be better.

We are replacing Statamic with Storyblock as our CMS for our frontend and with ALMOST EVERYTHING it does a good job as a simple, easy-to-use CMS for the marketing team to interact with. However I currently end up needing to manually copy content across multiple pages, which is a nightmare when it needs to be updated... Presets are cool, but only when creating; why can't I update the preset to all instances where I used that preset???

What I like best about Storyblok is its ability to handle complex content structures with ease. The intuitive interface and drag-and-drop functionality make it easy to manage and publish content quickly.

The pricing can be a bit steep for smaller businesses or freelancers.

Quickly build form to input variable and complex data.

High-quality visual editor with many customizable options. Offers extensive documentation and great API support.

Additional charges take place without any warning signs. Simple plugins that are needed for a basic website require paid plans.

Jamstack sites with easy content editing.

A very compelling model for building large websites.

The plugin system is quite rudimentary and not user-friendly (for devs or editors).

Building large websites with many editors and page types.

I think Storyblok is the only CMS with WYSIWYG functionality. Content editors always need this functionality while editing/adding content. Instead of clicking on many links to view the preview. Management API & CLI to update the component without actually going into the interface. If you are looking for a SaaS Headless solution for small and medium size projects then it is one of the best in the market.

User management is not mature enough for enterprise or medium size projects. As an example, it is not possible to have roles for developers. The Developer will have access to the administration of spaces. Management API should also be improved to use space in a classical environment fashion. It should also be improved to have multiple projects in one space.

SasS headless solution for both editors and developers.

One of the best features of Storyblok is the possibility to collaborate and create content internationally.

The flexibility and adaptibility has a cost. The use of Storyblok is not as easy as other CMS. Users need a bit of time to get acquinted with the UI which is not the most self-explained interface.

With Storyblok, we can create content internationally as well as local individual content without having to use different systems.

The beautiful way to organize my content. Really simple for the team to contribuate

Difficulties about the configuration of the multi-language

The possibility to have content personalizable to my website.

Component-based structure, ability to easily reference other entries, embeddable components within RichText and other components.

Still working through some editor experience bugs, no way currently to embed other entries in an entry, poor native table editor.

Storyblok is allowing our content and marketing teams to take control over organizing, arranging, and creating new pages with predefined components! This will help us move a lot faster.

Visually stunning for new users. Easy to grasp and work with once initial set up is complete.

Storyblok dos have some integration issues with other microservices. For example, Adplugg which we use for partnership ads is not working as designed with the embed card within a Grid in Storyblok. Confirming common microservices your customers is an effective policy. Focus on infrastructure polish (Javascript SDK + HTML5 Tags is Adplugg).

We want our administration to have full autonomy of how they use their websites without an engineer present for each department. This will be an improvement over drupal when fully on-boarded.

Storyblok has given our marketing team powerful tools for managing content on our website.

Having just updated to Storyblok v2 there has been a big update to the UI which will always take time to get used to.

Before our team relied heavily on outsourced developers to create web pages, now we can quickly create and launch pages internally.

Flexibility in building what is currently desired.

Buggy behaviour of editor resizing, fix it please :)

It doesn't matter what kind of page you are currently building for your site, Storyblok can handle it all :)

The ease to copy paste structure / share components, migrate data. The preview mode, structure folders!

I think user should be able to have a component in different folders at the same time, maybe by using a tagging system or something. It would allow for much more precise bloks contraints.

Using a CMS that's easy to use for developers, clear to use for clients. Not painful to work on structuration, simple yet complete.

User-friendly, very intuitive, anyone can use it without any kind of background.

Like all the CMS, changes are limited but the results are fine.

We use it for the main website of the company and we do not need people with coding knowledge to manage them, so we are more productive.

Live preview, support channels and helpful staff

Setup can be a bit cumbersome, clear guidelines for different setups would be great

Ease of use for the client and simple deployments means no crazy infrastructure setups.

Storyblok's flexibility in creating content types and presenting them via the API is brilliant, intuitive, and very straightforward to implement. The interface is fast - very fast, and the incredible power of components and blocks makes for a genuinely superior client editing workflow. I was able to get the data out of the API and spin up a working frontend in no time.

Migrating from another platform was outrageously simple and, in turn, an utter nightmare. Importing via CSV was super easy. Unfortunately, the documented methods for converting HTML to markdown, then markdown to rich text don't work out of the box. Although I managed to get half the process done (html to markdown), I was never able to make that final step to richtext - and with an esoteric request like this, I just wasn't able to get any support for the issue.

Storyblok provides an intuitive and fast editing experience for my clients that allows me to set constraints on the elements they can use and modify but allows them the freedom to create content as needed. It also frees me from the limitations of monolithic platforms, and provides an excellent API-first approach to front-end development.

The API has a number of options for filtering and querying. It's fast and concise. GraphQL support is great too.

Relationships in the API are poorly implemented and difficult to workaround. Even the GraphQL API was missing a relationship lookup aspect.

We needed to deploy a powerful CMS for a multimedia platform. The benefits was the visual editor which is a godsend for newcomer content maintainers.

The content model. It's simply unrivaled and what I always wished for. - Every other CMS our there still wants me to assign specific named fields for a content type instead of letting me use blocks of well-defined structure in a hierarchical way within a content item. - There are not only collections of types of content, but an actual hierarchy.

I wish there were more convenient ways to query *all* content items in a way that includes Caching. The grapthQL API - is not cached (as far as I know) - does not let me query different content types at once (when searching for fields that all of them still may have in common)

A typical corporate content thing.

Modular and quite useful once you understand it

We really like it but it takes a bit to get used to it, plus, it has required a lot of work from our dev team to make it useful

Less dependency from tech

The ease of editing copy, ability to edit and store copy in multiple langauges

The stacking/nesting of blocks and rows is tricky and not intuitive. It's very easy to delete or remove blocks on the interface and not be able to undo it.

Allowing wider team to edit images and copy instead of it needing to be engineers

The dashboard and tools are fairly intuitive and useful.

There was a rich text parser package available for React, but not React Native. This issue led to our team having to build an entire parser on our own. The visual editor was also not available for React Native.

Content organization.

It is possible to use any frontend framework.

Not able to create custom bloks that I can share with the world.

I am able to focus on the development and my clients can focus on the content.

Storyblok is a very user-friendly platform.

When finding the content to edit, sometimes it is hard to navigate the folders.

Things publish faster now.

I like the versatility of the components.

It's difficult getting things to go live.

Storyblok makes creating content easy and it makes our products look good.

User experience, flexibility to configure required layouts

Pricing model is not suitable for our business case. The cost for the service, in general, is too high for the value provided

Enabling non-technical users to edit the content of our company websites. So far Storyblok did solve such problem for us

Great tool. Like the real time component changes.

Not so great tool. Don't like the real time component changes.

Changes of data throughout the app

visual editor and fast previews with less dev

Not enough access to "cloneable" templates and components.

Faster publishing and less dev botleneck

I like how easy the blocks are to use. The copy and paste function is great when moving or amending pages. It is great if it is your first time creating a website and is simple to use with little training needed.

Storyblok isn't as compatible as other website builds such as WordPress or wix. A web developer is needed with a lot of more complex tasks and isn't as easy to install plug-ins. because the site is custom built, integrations aren't easy.

Storyblok helps us promote our services, having a detailed website demonstrating all our services. The flexibility of page creation helps deliver our messages.

- Easy to see what is being changed on a page - Always have someone at the other end to help figure stuff out - I use it everyday

- Search bar is improving (no more deleted letters when writing a search request) - But I still can't find what I want all the time - I have to be very precise and can't look for pages using simple keywords - I can't just click on the link of the live version of the page and have to navigate through our website to find it again - No tool to edit a page from front that takes you to back automatically (like Hubspot extension) - which experience wise was a great help

It gives us a back office interface to publish content online.

It's easy to use and integrate with projects

It adds a lot of latency/load time, requires app recompiles, and is not cheap

Easily editable content

the research bar works at best for finding information!

representation of the cms structure does not match the representation of frontend

translation mistakes of text preloaded in my language