Storyblok Reviews & Product Details

I like the excellent documentation and the easy way of receiving data from the backend I use it with NuxtJS to get serverside rendering and to get a good SEO performance.

I tried to use Storyblok as a backend for an App, but it doesn't work. Maybe it's not intended to do such things with it. I would like to have a user registration system built inside. It would be great if that is possible.

I think the primary problem at my old portfolio site was that the changing of the content was to uncomfortably. With Storyblok i´m ten times faster i think much better than a pure node

Visual editor community potential for growthè

Some features are missing here and there, but I'm optimistic for them to come in a later stage!

Creating a landingpages on an exisiting platform with the current technologies used + visual editor <3

Visual editor, live preview of content Intuitive in maintenance, nearly doesn't need any briefing for new people to understand how content is managed Flexible -> implementation of new features is really easy Inheritance logic for languages/countries

Nothing. Suggestions of improvements are always recognized by Storyblok.

We are using Storyblok not only for content, but also for promotions, redirects, shop configurations, merchandising and SEO stuff. Modular system and visual editor enables us to build content twice as fast as before.

The integrated live editor, which integrates seamlessly with your site

Not as mature as Contentful, for example it doesn't (yet) show you where a component is being used

We publish landing pages, it's quick and easy

Storyblok allows us to create schemas without any limitations. Its flexibility is unmatched. We were able to create a massive block-based website and it had a solution to every requirement we had – from advanced editor permissions, to its own image optimization service.

If I were to point something that's not great in Storyblok it would definitely be its dashboard. The UI (and, sometimes, the UX) could use a little work. It could also be nice to have a "repeatable" field that could allow us to create a single-use schema (instead of having to create a new independent schema and using "block" with component whitelist).

We're building apps and websites that allow more flexibility and independence for the clients

- Storyblok can connect to every tech stack without effort. - It's super easy to create new content types and retain relationships previously created. - The visual editor is what our customers love and what helps developers understand business needs - The whole product has a DevOps mindset which is very important in Enterprise: Workflows, backups, APIs. It's an invaluable tool inside every business process we have running - The image service is on par with dedicated image SaaS tools and fully integrated into the solution. More value for my money

I can hardly find anything to dislike. Every experience from setup to support has been nothing but positive.

Maintaining customer sites of all sizes from small landing pages to multi-page documentations (2500+ pages). The immediate benefit I got was a true separation of concerns: People start managing content again, creating heaps of knowledge without being forced to think about representation. But due to the excellent visual editor, you literally never lose sight of the final result. This is UX at its finest Focus on the core task, make aware of the entire picture. Due to the unique separation of content into separate units called Bloks, content teams are faster than never before. The content becomes a manageable mesh, rather than a deeply nested tree of pages. Content creators can navigate a lot easier.

- Setup is very easy and documentation with real world examples is very helpful - they provide tools for every stack. - Editing content with 100% live preview is unique and just impressive. - Very powerful in terms of extending your own logic. With custom components (tiny vue application you can import) and api's you can achieve probably everything. - Translations / internationalization just works. - API is incredible fast, so far the timings where about 20ms. - Workflow for releasing content is very well thought through - you can group content and apply a scheduled release on this groups. - Support is awesome - you will get live chat support within minutes. - Many features, that we didn't even think of.

I missed some minor features like ui improvements. Some of theme are already implemented, for others a feature request has been created.

For the relaunch of our international e-shop we needed a api driven cms, that is highly customizable. We were able to synch the existing category tree of our e-shop easily. Internationalisation is very well thought trough - one of the features that i missed in other cms. Thanks to the live preview our content team is now able to maintain content twice as fast. So far for all problems, we found more than one solution how to solve it - you have the freedome to choose.

it's simple to import pictures or insert info. the difficulty is that you are not able to move from a page tot he other .

it takes to long to upload the info,. there is not a way to go back to the former page ...must of the times you need save and go back to the home page. if you need to upload a lot of info is not a friendly system.

it's manageble for the company

Storyblok is easy to sell to a client because they also provide materials tailored for content editors and marketers people. This set them apart from most CMS that usually focus too much on the developer experience. Apart from that, the king feature is the visual live editor mode. After a quick demo, clients buy the idea quite easy and I can start doing my job.

I would say that their Graphql feature is a bit disappointing. I started from there but switched to using their own SDK APIs some of the functionalities didn't work as in a 'standard' Graphql API service.

I'm allowing Charites to manage their content and adapt their donations campaigns without needing too regular help from our development team. The visual editor helps them to understand what to do without having any technical background.

Storyblok is the most intuitive and seamless webste building system I have used to date. The page creation is fast and simple with clear steps to creating an efficient webpage. I largely use the pages to promote events and the layout and set up is always consistant and effective.

The only thing about Storyblok that I find less then ideal, is the number of steps required to set up certain elements on the pages. The menu navigation can take a bit of getting used to.

We are able to promote our gobal event schedule in a consistant and effective manner, to all audiences. Updates and page builds are quick enabling us to keep up with our busy schedule.

As a CMS is super. Create, edit and change content is easy but coding for storyblok isn't.

The blockLibrary is a bit messy but nothing critical.

As a Headless CMS it was easy to implement it into our System and use the stories for deliver the content.

As a user of Storyblok, an advanced headless Content Management System, I'm impressed by its user-friendliness and flexibility. I find it exceptionally easy to use, which both my clients and I greatly appreciate. With Storyblok, I now manage multiple websites smoothly and efficiently. The editor is a true boon for my editorial team, thanks to its intuitive interface. For me as a developer, Storyblok also offers numerous valuable resources and a well-thought-out logic, greatly facilitating my work on various projects. This combination of ease of use for editors and powerful tools for developers makes Storyblok an important tool in my daily work.

While Storyblok offers many advantages, there are some downsides to consider. One significant issue is the cost; it's not a cheap solution. This can be a deterrent, especially for smaller businesses or individual users who are budget-conscious. Additionally, the sales approach can be a bit aggressive, with a persistent push towards the larger, more expensive packages. This can be overwhelming and may not align with the needs or budgets of all customers, leading to a feeling of being pressured to upgrade beyond what is necessary for their specific use case.

Storyblok, as a headless Content Management System (CMS), excels in its ability to efficiently manage content across multiple websites from a single backend. This feature truly capitalizes on its headless nature, allowing for seamless content distribution and updates across various platforms. By centralizing content management, Storyblok eliminates the need for duplicating efforts for each website, leading to a more streamlined and efficient workflow. This approach not only saves time but also ensures consistency in content quality and branding across all digital properties. The flexibility to serve different front-ends while managing content in one place makes Storyblok an ideal choice for businesses looking to maintain a cohesive online presence across multiple sites.

- Have own field plugin(have a react support) - Ez to work with next.js - User friendly

- Moving stories look a little strange(how about drag & drop?) - Sometimes UI Looks over load

works like a CMS, to have a good result for the Content creator and make dynamic pages

I like that storyblok has a view-in preview thats built in on the page so i can see what i'm doing already and not have to go to a different tab everytime. It is also Headless which makes it easier to separate frontend and backend activities which is better.

I really don't like the version 2 at all. The UI changed and it looks more to me like a child's game. every thing is reactive and has this excessive scroll on tap feature. Feels like a game. version 1 was really nice but sometimes you cannot see the text, this only happened after v2 was released.

we use it to manage all the websites in various country affiliates we work with

Honestly the best feature of storyblok is the help desk. You can do so much with the whole system and it looks great, but the speed and thoroughness of the help chat on their website makes creating and troubleshooting complex components a lot easier.

It's a bit of a learning curve and figuring out how your setup is compatible with the headless system and there aren't necessarily comprehensive exemples for every framework.

With the visual editor and easy component creation it's just miles ahead of other systems. It's a lot easier for our clients to be in charge of their own content and change things on the fly.

It's thought trough product, were for a lot of things are covered and from content managment perspective developer doesn't have to create new bicycle.

Documentation for APIs can be updated and for extensions especialy, better examples could be provided how to create them, because currently DX is not the best. Then again, cool ideas are integrated in Storyblok.

Content creation and its managment for dynamic pages, created on Sb, were content editors can do a lot of stuff with pre-defined components, without developer assistance. Reduces a lot of developer time to assist creating basic landing pages or changing texts.

The overall architecture & design of the CMS works flawless. Besides some technolgoical issues in the beginning, the technical integration & project setup worked very well. Also the overall usage inside the CMS and the content editing is simple and fast. Especially for my clients.

Sometimes i need too "hack around" some of the functionality. But i believe that comes from the architecture itself. Also the documentation regarding specific technologies is a little outdated. Took me some tinkering to get everything working.

First of all the overall headless approach solves the "backend developer problem". Because you can configurate your backend, you really only need the frontend part developed. Therefore you have huge savings in development & planning time. Also most of the CMS are bound to internal restrictions. Storyblok does barely have any of these restrictions which leads into a lot of flexibility for me as a developer and also for my clients who build pages & modules in the future.

From my point of view, Storyblok provides quite a lot of potential for an easily customizable CMS solution. Integration via JS storyblok bridge is easy as well, if completely customized behaviour of the api is needed, an own connector can be implemented as well.

While implementing Plugins (applications) for storyblok we stumbled upon how to manage settings for plugins. Here it would be very helpful to have a starter project, which already provides the settings part. Then it would be easier to start with plugins, which need additional settings.

Storyblok provides a scalable, easily customizable CMS solution. We are using it in several MACH oriented contexts as the CMS solution and are mostly very satisfied.

- Pretty easy and accessible to use. - The free community plan has enough features and space to use for a personal blog or website.

- Sometimes the Richtext rendering is not optimal.

I created a personal portfolio and blog website. Using Storyblok has helped me to organize and write all my blog posts while offering the freedom to implement my custom web design. For example, in my home page I created a slider to show every project preview I made, then the single project slide would link to its dedicated blog post.

I like how everything is in blocks so you can easily use templates to keep the website fresh. I also like how the developers know when something isn't working. They set up alerts.

The previews never work and I can only reorder stories on my phone. I can't do it on the desktop. Sometimes it takes a long time to load changes but normally it's fine.

We did it to improve seo and make the user experience better. It's new but it seems like it's better than the messy website I created in the past.