Storyblok Reviews & Product Details

The interface is making Storyblok easy to use despite the huge quantity of options and possibilities

Some data can sometimes be painful to retrieve via the API and needs several API calls to fetch

The ability to get data easily via the API and create and edit content in an easy way with the website interface

How easy it is for the client to understand the CSM

The invoice process to cliens. I think it can inprove a lite bit.

As a gency. storyblok credibility is very important to our customers and which customer use Storyblock. The client feel that it is a platform they are willing to take on.

For starters, its learning curve is initially gentle, allowing users to easily start implementing stuff from the very beginning. However, after using it for some time, you begin to discover the powerful features it offers, expanding the initial possibilities to a new level. I really liked the navigation approach for creating stories, the available plugins that enhance the capabilities of the system, and the ease of creating new plugins by myself. I also like the easy it is to configure different live preview environments, the webhooks functionality, the many approaches you can follow in regards to internationalisation, the flexibility on how to retrieve the content with its APIs. I've been instensly developing for customers using Storyblok for the last year, and both my experience and the feedback from my customer's have been great.

I'd love to have the possibility to define content outside the navigation tree. I don't like stuff like configurations stories to be "using" a route that could be used by the customer, potentially breaking the application. Besides that, I cannot thing of any big issue with it. Of course I'd change some little things, but in the end they are small details that are not affecting the day-to-day development with the platform.

It allows us to develop really fast based on the requirements given by the customer, making it easy for us to show results to the client in just weeks (if not days), and thanks to the live preview, it helps getting our customer feedback very soon, so we can improve our solution together.

The most helpful is the ease of use. I onboarded content managers really in minutes and mostly they needed not more support.

Some parts of the navigation is a bit different than in other apps, so it needs some learning curve, but if understood very clear.

We have several digital channels and want to create a unified content strategy for all these channels and a first step is to find a place for all contents and share them between each other.

The implementation of Storyblok is based around ATOMIC design principles which allows a component first approach and makes it easy to implement. The custom fields plugin which is part of the application allows you to build content from other APIs into the content of your page or Blok and makes it the perfect itegrations addon. Along with the Live Preview for each environment, Test, UAT or Prod, makes this the best in class!

Some more case studies and code based case studies would be great!

The seperation of the CMS is important to allow frontend developers to keep your website fresh. Storyblok is fast and very scalable!

With Storyblok, it's incredibly easy to amend content on the site, everything is organised and with a well-set up site, almost no team training is required. It's also incredibly easy to integrate all of your core applications.

I've not come across any downsides to Storyblok. I guess I wish we could integrate Bynder without having to upgrade.

Storyblok allows us to quickly and easily create content for our website and allows us as an internal marketing team to manage the whole site without having to rely on developers.

The reusability and the design system that Storyblok boasts integrates itself seamlessly into our way of working and our codebase. We've created more than one site using the same library of components and now simply seek improvements to the way that we're working with these components - and the spaces that utilise them. We use Storyblok every day as part of our work, whether it's developing a new feature or just creating a funky new page to show off the art of the possible. It's been so easy to create new content on the site that we find ourselves - even as developers - making fake content pages just to show off the work we've done and what can be acheived with it.

V2 fixed a lot of the quirks and problems that we'd previously noted. It's a much slicker experience. My least favourite part of Storyblok, however, is how the Releases app seems to be a bolt-on to the content creation process. There are still inherent bugs and quirks with getting it to slot nicely into our spaces. For our teams, it feels absolutely vital, so it'd be nice to see it get more of a focus.

It encourages the creation of reusable components that can be inserted within each other. This aligns with our development principles and ensures that we are not making everything bespoke, saving us time and also allowing the content teams to experiment more with what's available to us. That in turn leaves us with less pressure to guide them design principles.

From a developer perspective I really enjoy working with the technologies used. Libraries are available open-source and are always updated for use with various technologies. Support is quick, helpful and very engaged.

On major upgrades or launches of new libraries, documentation and source code sometimes don´t match, but that´s just a minor issue.

Providing an CMS with up-to-date APIs and technologies, supporting all our needs.

I recently had the opportunity to work with Storyblok for an ecommerce product MVP, and I must say that my experience with this platform has been nothing short of fantastic. Developer-friendly GraphQL API: The schema is well-documented and easy to understand, making it a breeze to query and manipulate data. I could retrieve exactly the data I needed without any over-fetching, which is crucial for optimizing performance. Intuitive UI and UX: Content editors and developers will appreciate the simplicity of the interface, making it easy for non-technical team members to manage content with minimal training. The real-time preview feature significantly streamlines the content creation process. You can see exactly how your content will appear on the live site as you edit it, which is a game-changer for developers working closely with content creators. This results in fewer iterations and a faster development cycle. Content localization and versioning: Storyblok's built-in support for content localization is a lifesaver, especially for ecommerce projects targeting international markets. The ability to manage content in multiple languages within the same project simplifies the process of creating a global presence. Furthermore, Storyblok's versioning system ensures that you can track changes, rollback if necessary, and maintain content consistency across various stages of development.

The GraphQL API documentation is not always up-to-date and this can be improved.

Storyblok simplifies content management for developers and non-technical team members. It streamlines the process of creating, editing, and organizing content, reducing the back-and-forth between developers and content creators.

Easy to understand and smooth. Barerly needed an introduction.

Nothing really. Every feature i need is there and the integration was easy.

Easy and smooth updates of our webpage. Easy to maintain a good design.

Great preview feature that makes a difference comparing to other CMS platforms.

Minor bugs. I can live with them as they not break the overall experience.

When we were looking for a headless CMS solutions, there was nothing to compare with Storyblok reagarding flexibility, ease of use and the amazing preview feature that makes the introduction of new content much easier.

The single screen view of all of the tools a content editor would need makes life so much easier. The preview allows editors to make good design choices but still allows devs to put constraints around those choices.

It is a struggle to find anything I don't like about Storyblok v2. If I was to be picky, I would say the focus tool on the images could do with a preview showing different ratios. Something similar to https://jonom.github.io/jquery-focuspoint/demos/helper/index.html.

Trying to find a way to rapidly publish content has become easier with Storyblok v2 and Gatsby Cloud Hosting. As I have a static site, publishing content is fast, almost instantaneous.

I like the design and that the CMS remains being very modern. I love that I can search for a page now inside a folder, and not overall the pages.

The prices are very high. It's sometimes difficult to sell this to our customers, as they would prefer a free CMS like WordPress instead.

I love that I can choose my own dev environment with Storyblok and always use the newest technology with it. I love that it is so fast and the editing experience.

One helpful aspect of Storyblok is its intuitive and user-friendly interface, which simplifies content management and allows users to create and update their websites with ease. An upside of Storyblok is its flexible and scalable nature, empowering users to seamlessly manage and deliver content across various platforms, resulting in enhanced efficiency and a streamlined digital experience.

While Storyblok has numerous positive features what can be disliked is that Storyblok can be relatively expensive for small businesses and individuals with limiting budgets.

As a headless CMS, Storyblok benefits users by decoupling the frontend and backend, enabling faster development cycles, improved collaboration between developers and content creators, and the flexibility to deliver content to various frontend frameworks or devices without constraints.

Storyblok provides a fantastic user experience for our clients. Visual editing is superb and way ahead of the competition.

The exposure of the platform is not so well known.

The ease of providing a working and simple to use CMS for clients.

Storyblok CMS has revolutionized my content management experience with its remarkable features and intuitive interface. As an avid user, I am thrilled to share my positive experience with this platform. One of the standout features of Storyblok CMS is its visual editor. It provides an effortless way to create and modify content. The drag-and-drop functionality allows me to arrange elements seamlessly, giving me full control over the design and layout. This visual editor has significantly reduced the time I spend on content creation, and I can now focus more on delivering high-quality content to my audience. The documentation provided by Storyblok CMS is exemplary. It is comprehensive, well-structured, and easy to follow. Whenever I encountered any questions or needed assistance, the documentation came to the rescue. It offers clear instructions and examples, making it a breeze to implement advanced features and customization options. This level of support has been invaluable in streamlining my workflow and ensuring a smooth user experience. Another aspect that sets Storyblok CMS apart is its partnership program. Their program is designed to foster collaboration and mutual growth, offering valuable resources, training, and support to their partners. Being a part of this program has not only enhanced my skills but also opened up networking opportunities with like-minded professionals. Storyblok CMS truly understands the power of community and has created a platform where everyone can succeed together. The extensibility of Storyblok CMS through plugins for Shopify is a game-changer for e-commerce businesses. Integrating the CMS seamlessly with Shopify has allowed me to harness the power of both platforms. The plugins provide a wealth of additional features and functionality, enabling me to create a dynamic and engaging online store. This integration has undoubtedly elevated the performance of my Shopify store, enhancing the overall shopping experience for my customers.

While Storyblok CMS has numerous advantages, there are a couple of areas where improvement could be made. Specifically, the documentation for the storyblok-react library could be more extensive and detailed. Although it is still helpful, a more comprehensive guide would greatly benefit developers working with React. Additionally, dealing with deeply nested relationships can be challenging when using the REST API. The process of fetching this data sometimes requires additional effort and can become complex. Simplifying this aspect of the platform would be highly beneficial, as it would improve the efficiency and ease of managing complex content structures.

By using Storyblok's headless CMS, I can easily deliver content to different channels and platforms while maintaining consistency. Whether it's a website or a mobile app, I can ensure that the content is up-to-date and accessible across all devices. This level of flexibility and agility greatly benefits me as a content creator, as it allows me to adapt to changing trends and user expectations swiftly. Moreover, the headless architecture of Storyblok CMS enables easy integration with other tools and services. I can seamlessly connect Storyblok with external systems, such as e-commerce platforms like Shopify, CRM systems, or marketing automation tools. This integration capability expands the functionality of my content management system and empowers me to create personalized and dynamic experiences for my audience.

When we use Storybloks visual editor, we can make changes and see how they look without having to save them at the same time. There are a lot of front-end frameworks that Storyblok can work with, which is good for us. These content blocks make it easy to write content for even the most complicated projects. This app has a lot of them. In Storyblok, we can change our photos to make them fit on the web and in apps. It lets us make our content work for people from many different languages and countries. Our team likes using Storybloks internationalization and localization tools because they make it easy to write content for a global audience. When we want to get to our data, we've used GraphQL API. It is good for the community, for developers, and for people who want to use it. It has a lot of support for a lot of different programming languages and frameworks. As a publisher, it's easy to choose a component because it's simple to use and can show a preview of what it looks like. Using the JSON format, you can get to their APIs.

From technical perspective, adoption requires time and effort as there are multiple type APIs and building seamless UX with the live preview editor is not an easy task.

Easy to use solution with a great UX that everyone can enjoy, from programmers and writers to marketers and everyone else who works with the site.

I like that is easy to navigate and insert building blocks. It was also easy to duplicate the pages and make the new ones. I am not advanced page builder but still managed to do it quite well!

The tool had certain bugs. For example I couldnt log in to change the pages from my account for a very long time. Also I had problems logining in from safari. It only worked in Chrom

Building landing pages and websites! It benefited because we have a beautiful website now. And it was quite simple to do it! was satisfied with it. In general the tool id good!

From my perspective, choosing a CMS has always been a compromise between having a flexible visual editor to build engaging landing pages while still being able to define the guardrails and roles/permissions to ensure consistency of UX and UI. I appreciate the all the aspects of the tool that enable flexibility within the context of a given user's role/permissions, which enable admins to present only the relevant and necessary functions and access for that given user's jobs to be done and scope of work.

Quite honestly I do not have any complaints at this point, I think the only challenge we face is ensuring that moving forward our marketing team has the development resources to fully leverage the features and benefits of the platform, but this is an internal question and not a dislike of Storyblok.

Storyblok is enabling a self-service model for our team (as well as other internal stakeholders) to regain ownership of particular content sections and user journeys. So long to the days of our website being a black box where the update, maintenance, and execution of new content and marketing initiatives requires long waiting times or development resources. Storyblok equips our team with a powerful and flexible set of tools that can be tailored to each users role and responsibilities.

The best upside is that marketers can easily use it and learn it. It also saves lots of developer hours due to it's easy to use interface and user friendliness.

Not much to dislike about it. I wish I was able to find some answers easier in the lots of documentation created but otherwise I think it's just a perfect CMS that can be used by any business.

It helps to save time and cover lots of issues when it comes to efficiency in the market due to it's internationalisation, and easy to use and learn features that are out there.