Storyblok Reviews: 4.5/5 — Highly Rated

Storyblok's visual editor is its competitive edge over other headless CMS. The preview experience was top-notch. It was easy for content editors to move UI components around and update the page layout without developers' assistance once they have set up the content components according to the Atomic design principles. For developers, the component bridge abstraction was so magical. Mapping CMS components (bloks) to components in the codebase was a little confusing initially, but once you get the hang of it, everything is so smooth. Developers can focus more on developing the UI components rather than figuring out the nuances of getting their components to work within Storyblok

When we started using Storyblok, the documentation could be confusing and disconnected. Discord's support was somewhat spotty; answers to questions aren't always immediately available and can fall into a black hole if no follow-up was prompted. But from what I have gathered, Storyblok has put more resources to address this. Storyblok offers both REST and GraphQL API options. However, at our time of development, there was a heavier emphasis on their REST API documentation and support, so we decided to go with REST vs our preferred GraphQL

Content management systems used to be where you had to install and set up clunky CMS platforms such as Drupal and WordPress. Provision and secure database setups using MySQL and all that. With Storyblok as a service, all of that is taken care of! No more worries about why the server is down, and platform plugin compatibility. We used Storyblok as a headless CMS and were able to reap all the benefits that came with a composable architecture, creating a dynamic website using our favorite language.

Storyblok is a CRM that offers editors exactly the usability and flexibility we need. The switch from Wordpress to Storyblok was easy for us. Content can now be played out even faster and more flexibly - and with much improved performance. Many free plugins provide seamless support for special tasks. Working with multiple editors runs smoothly, as workflows can be defined yourself. Headless technology easily delivers content to different devices.

Some hick-ups depending on server configuration, but can be solved.

Usability and lack of performance

The best about storyblok is the way the ui is friendly for the end user but also with the developer that helps allot in the part of delivering a finished product to the client and how the client understand easly the way to work with it

I think if there are so many blocks can be a bit difficult to navigate between then but with the v2 block searcher it got a lot easier, and the initial prices are a bit high for countries with small economies

We use story to give the old cms a new and renovated frontend but keeping the strong backend of them and also giving the client an easy way to edit the contents of it

It's user-friendly and fast, the live view is really useful and the drag&drop feature is a standout functionality. It's possible to create complex content quickly and easily, without using manual codes.

The CMS is very user friendly, but sometimes there are too many clicks to finish an action. Navigation through sections is sometimes confusing. It's quite easy to get lost in the UI. The price is quite high.

Flash page speed on Google, also it saves time allowing to focus on the content and not the technical side of the project.

You get the programmer to program each component how it should be, that way the client has less chance of breaking it or messing up font size/type etc.

You will need to hire a programmer for this to work.

It's less likely to break because the programmer programmed it to only do certain functionality. You won't have issue with mix font type/size or using wrong colour.

I absolutely love the flexibility and ease of use that Storyblok offers. It has a user-friendly interface that makes content creation and management a breeze. The modular approach to content blocks allows us to create reusable components, saving us time and effort in building websites. The real-time collaboration feature is incredibly helpful for our team, as we can work simultaneously on different sections of a project. The vast array of integrations and APIs also make it seamless to connect Storyblok with other tools and platforms we use. Overall, the scalability and customization options provided by Storyblok have greatly enhanced our development process.

While Storyblok is an exceptional headless CMS, there are a couple of areas where it could improve. Firstly, the learning curve can be steep for beginners who are new to headless CMS platforms. Although the documentation and support resources are extensive, some additional onboarding materials or tutorials for newcomers would be beneficial. Additionally, while the pricing structure is reasonable, it might be slightly on the higher side for smaller businesses with limited budgets. However, considering the robust features and the value it provides, it is still a worthwhile investment.

Storyblok solves the problem of traditional CMS limitations by offering a headless approach, empowering us to use any frontend technology. It streamlines content management, saves time, and enables real-time collaboration. The robust API and integrations ensure seamless connectivity, benefiting our workflow and enhancing our website development process.

Storyblok has several features which I liked and they include the following: It has a headless approach which is appealing. It also has a content editing interface which is so easy. It also has content versioning and collaboration which allows multiple people to work on them. It can also be integrated with other software.

Storyblok has the following downsides: Limited template options. There can be performance concerns by some users. Its pricing structure is also high for some people . Its need for internet connection.

It has helped in alleviating lack of content management. This has enhanced the quality of work I produce.

Easy of use for clients, but also ease of use for developers. Time to market is really fast. They offer good support and have a good partner program.

Nothing much to dislike, during development we sometimes ran into some issues but with a little support they were fixed quickly

Ease of use for our clients, have a live preview/editor available during content management. As a developer the time to market abd ease of deployment really was benefitial.

Best part are the accessible UX and UI, workflow and approval features. Customer support and new features and improvements are the cherry on top

There's not much but assets management can be improved as we currently tend to create duplicates content...

Centralized place to store and maintain organized data across different teams

Storyblok offers a wide range of benefits that make it an ideal solution for content management and web development needs. The visual editor, with its drag-and-drop functionality, is a standout feature that allows users to quickly and easily create complex content layouts without the need for manual coding. This feature alone can save users a significant amount of time and effort, enabling them to focus on creating high-quality content. Additionally, Storyblok's component-based approach to content management makes it easy for teams to maintain brand consistency across all pages of their site. By reusing components, marketing teams can ensure that all content is consistent with their brand guidelines, creating a cohesive user experience for their visitors.

Searching content can be hard sometimes when you have a lot of data and adding filters takes too many steps.

Some centralized places when all teams can enrich our data and at the same time use the same data structure

UI live preview and scheduled changes really differentiate from competitors. Customer support is also really responsive!

Some time a bit slow to load but not sure where the issue is really

Centralized content management with good user/permissions settings

Great to start quickly without developers, as we would expect from a modern SaaS application. How content workflow an translation works mets our requirements quite fine!

It is missing more dashboards on usage and contents generated (how many stories of each type over time, etc.)

Centralized and international ready CMS for our e-commerce platform

The platform's flexible API, well-documented and clean code, easy integration with popular frameworks like React and Vue.js, and powerful SDKs for customization.

While the platform is developer-friendly, some features may require additional configuration or custom code, and the pricing structure may not be suitable for small projects or non-profit organizations.

Storyblok solves common content management challenges such as maintaining consistency across multiple platforms, managing complex content structures, and enabling collaboration among teams. The platform's modular approach allows for easy content reuse, reducing duplication and saving time.

User interface that get better with v2. The asset manager with images processing work nice.

So far, nothing really for my usage (portfolio) except maybe for a missing first pricing tier?

Manage large medias types and hosting included

As a Marketer, it helps me easily and independently update our website and blog from a single place.

There is a bit of a learning curve to understand the logic of how to use it. However, once you get it it's easy and straightforward to use! When editing blocks it's sometimes not easy to visualize what changes you are making. You have to flip between the editing blocks and the preview page which sometimes is a bit time-consuming.

I can independently update the website and blog without requiring help from my engineering team. Once it is set up it is easy to use! I am a Marketer.

The Visual Editor, the generous limits in content types, locales,... and the speed of the tool.

We sometimes have bugs and they take time to resolve, the assets manager is hard to keep tidy and the integration of Storyblok in the code takes time at first since you need to set up the visual editor bridge.

Giving content editors full ownership of the website content while providing a great integration experience for developers.

- Easy to set things up if you just want some resources and pages - Easy to use for editors - Easy to do a POC - Easy to demo the added value to a client - Easy to explain to users that has already used concurrent CMS like Contentful

- Some tutorials or documentation are unclear if it's the old or new version of Storyblok API - Hard to find information about global components - Edit "global resources", like "Project" that can be displayed as a card or as a page

- Preview of the actual compoinents in a page content - Draft pages - Easy website workflow using webhooks and NextJS ISR - Export components that permit to share the "SEO" component between projects

1. Storyblok is easy for technical and non-technical people. 2. We can easily set up roles, permissions and restrictions. 3. Storyblok has an excellent way to log changes. We can easily track the changes made and who made them 4. The UI and UX is really good.

- At times, the management API is not very dependable. Its behaviour can be unpredictable. - Search functionality is not that usable. You often cannot find what you are searching for, which can be challenging as we have thousands of pages on Storyblok. - Upgrades are not always backwards compatible. After the Storyblok V2 release, some of our features broke, and we had to roll back to Storyblok V1 and fix them before we could have our users enjoy Storyblok V2

Storyblok has helped us to ensure that each department can focus on its expertise. The system has enabled us to improve employees' overall job satisfaction as it is user-friendly to both technical and non-technical people. It has also reduced a lot of mundane work. It has also helped us to launch more products way more quicker.

It is very easy to use. Every team member can work with it. Even if you do not work as a back-end developer, you can choose what you want the page to look like.

That our back-end developer team has to create a lot of templates before we can make use of them. This is a lot of extra work that sometimes does not allow us to make something look pretty, fast.

It saves a lot of time. In systems like Wordpress, you need to spent so much time on making sure that everything fits nicely and looks good. With Storyblok you van just add components really easily.

- The new 'Search blocks' feature. It will save a lot of time, especially if you handle a lot of small and same-named modules. - The new primary Color - The Basic Idea behind Storyblok

Editor Interface: There is no focus or priority in design - same margins between elements, font sizes, same contrast, no buttons. You removed the focus of the last used element inside a list. I need to do more clicks than before - e.g., multiple lists (why should I additionally save a selected list?). If I allow only one specific block, I have to pick it inside an overlay before I only need to click on 'add block' I need to move more with my mouse - the overlay for adding blocks is now in the center of the screen - before it was close to the button, I clicked before it was way more intuitive - the reason our content creators loved the interface The position of the error message for missing content is unuseful - I need to search for it. Blok Library Editor is not always working - sometimes it does not save changes Editor Interface of field-type blocks: - the most used feature is now at the bottom, allowing only specific components to be inserted' - and barely noticeable because I need to scroll now, and it sticks to the bottom of the screen Assets: Why do you hide the folders behind a button? Again I need to do so much more clicks to finish my to dos No drag and drop for sorting your assets Spaces Page - the cards are way too big; I need to manage more than ten small Projects; before, it was a nice list General: You must go back to a clean and focused design approach. Think about visual priorities. V1 looked a little bit old-fashioned, but you delivered a great experience. Remove a lot of that clickibunti stuff, and you'll be fine.

- Asset management - Manage a lot of small projects with shared components base - Use the role management to allow customers to manage the content by themself (they can be really picky)

The live preview is something my customers really like and me and my colleagues aswell. It's also easy to clone from one space to another early on in development.

Sometimes I find it abit tedious when adding content to my modules. There's alot of steps involved going back and forth. Perhaps getting back to the main module when you've completed all fields for a subfield.

It's making my customer's work easier and hence makes them more satisfied. I also find it much easier testing on QA with the live preview. Setting up new pages is also very easy and done quickly.

Its flexibility and the new collaborating assets to use as a team.

We use Storyblok with Shopify and to do so we had to create our own Shopify/Storyblok connector. I think there is one in current developpement but meanwhile we're stuck with no solution.

The Shopify/Storyblok connector, more flexibility and content for WYSIWYG editor for items like blogs

Easy to use, and highly customizable, the plugin and app features make room to expand content fields as we need, making custom fields helped with authorial icons and assets library. Amazing tech support, fast responses and fast solutions.

We need a way to find unpublished items that cause problems when using fields with relations, like when using Stories type in the single-option field. Sometimes the search bar is too accurate, if I don't remember exactly the slug of a story, I can't find it by containing words, for example: searching for "pages test" won't find the page "pages/developers/test/"

Managing assets, stories and multiple websites of our company. Editors can work without the need of the developer team. Our deploy time is almost 90% faster using Storyblok + NextJS

Intuitive UX; visual preview; block sear

Requires dev; cannot integrate without coding

Evolving fast to desired online experience across channels

A very good headless CMS with great preview function. The visual editor simplifies the collaboration with the editors. Especially working with Bloks is super pleasant, so all requirements of the editors and designers can be implemented. Atomic design can be implemented super through the blocks. 

Through a folder structure, we can build content analogous to the website. This way, editors can quickly find their way around. 

The support is also very good, you get fast and competent help.

Through our project we often encountered challenges like flexible header / footer menu structures, here I would be grateful for a defined design option from Storyblok. For example with even more data types.

With Storyblok we combine an online store with classic landing pages where different products can be advertised or simple content pages can be created. This way we can exploit everything with one system.

Visual editing of content, fast response, plugin architecture. Easy copying of content.

Adding a block takes too many clicks. Using reusable components is not very user-friendly. Only one developer can work on the same plugin (owner is developer)

Taking too long to design a page. Hosting the content. Not having visual preview of content.

Easy integration with most common front-end frameworks for Developers. An easy-to-use visual editor for (end)users.

Initial setup can be tricky at first, but help is always available.

Building headless websites and apps, without compromising on user-friendliness and development speed.

The new management, search, content sidebar, and image capabilities are enhanced and are much better than before. It's a great, easy-to-use product and I find it easy to work with.

The new way of adding multiple choice answers on a block is a little weird and took a little time to get used to - it's not obvious what the difference to the old version is at first but once you get how it works, it's a little annoying as you discover an extra step is needed.

We love Storyblok as it is a great headless CMS for our websites and with multiple users from different backgrounds and capabilities able to use it, it's a great addition to our suite of tools.

Storyblok is the ideal solution for anyone searching for a headless CMS that can integrate various critical business elements on the site. We really enjoy the freedom of how we can design our website exactly how we vision.

There is very little I dislike about storyblok. So far I haven't met anything that annoyed me. Although it is somewhat important that you have a great team of both developers and marketers.

We were searching for the ideal solution to create our new website. It should bridge the developers and the marketings vision for our website. Here, Storyblok solves all our challenges and we were very satisfied with the CMS in general.

The user interface feels snappy and well thought out. The visual editor works really well to preview updates in real-time. The number of blocks you can use is really generous. The JS SKD has worked really well and TypeScript types really helps.

It would be awesome to be able to codegen the types for different block types based on the Storyblok configuration. Now we have keep them in sync in the code. The visual editor can get a little busy with all the tools available on a single page.

Storyblok empowers content editors to make changes to our website without involving editors. From the developer's point of view, we can limit how the site can be customized so we can make sure the site works well.