Storyblok Bewertungen und Produktdetails

It's live preview and customisable Bloks have allowed us to present editors with their content in real-time. The custom field plugin allows developers to create their own integrations in the CMS! Storyblok also compliments Next.js perfectly well and we have the choice to either pull data at build or fetch in real-time giving us the choice of SSG, SSR or ISR.

Documentation could be more in depth and contain more examples.

The live preview has helped Content Editors deliver reusable content more efficiently and has solved the last issue around which CMS to use with Jamstack. Custom Fields allows us to integrate data from other API's into our content and it

Our clients love the live editor, that's been a game changer for us. Also really love how easy it is to add new blocks to content types, and new fields to blocks, I like how you can access that functionaliy directily from story you are currently working on, this saves our developers a lot of time.

Sometimes it's a little slow to load, lack of utilities and helpers for React/Next.

Quick for our devs to get started on a new project, not having to worry about migrating data or running php/docker locally saves us so much time. Easy to use interface and content/block structure means or devs get familiar with how things work in Storyblok much faster than other CMS's.

The modular approach allows for effortless content management, while the visual editor streamlines the process, enabling a dynamic and efficient workflow. Additionally, the robust API support and collaboration features contribute to a smooth and collaborative development experience.

There are challenges in terms of complexity during initial setup, involving understanding stories, spaces, content types, and API usage. There are also challenges with bulk edits, GraphQL API limitations, and an initially overwhelming interface that hinders the ease of use.

It allows for seamless content management, enabling developers to efficiently organize and update content without compromising website speed. Its modular approach empowers developers to design and structure websites flexibly, ensuring a tailored and efficient architecture that aligns with specific project requirements.

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.

- 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 live editor, it's easy to understand, the community support

It's not flexible in terms of having global reusable data. the bloks return an Array even if the min and max is set to 1. The migration of existing data into a new structure is only possible with the API and it's not user friendly.

Creating a structure for our data. Letting the stakeholder manage the content.

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.