Storyblok Reviews: 4.5/5 — Highly Rated

The idea behind the product is solid, the visual interface is pleasing and relatively intuitive, the documentation (while sparse or out of date in some areas is somewhat comprehensive).

I wanted to like Storyblok and tested it with a proof of concept marketing site, but ultimately found that it is unsuitable for production use by most organizations. I genuinely don't understand how any large organizations are using this effectively. Fundamental things are not supported or don't work correctly, and the support staff I have interacted with, while friendly, are essentially not knowledgeable of the technical aspects of the product and make suggestions that are either not possible, not working, or irrelevant. The last conversation I had with support was over a week ago, and they said they would "get back to me with answers." Since then, I've followed up twice via email and heard nothing in response. As a paying customer, I expected better and will be seeking a refund.

Allowing non-techinical staff within my organization to customize marketing sites based on components developed by our frontend-engineering team.

I like the flexibility (also a weakness), the editor, the fully-fledged image handling solution and the plugin in system. It is a good bridge between developers and content writers (in theory)

The main thing that makes me angry about storyblok: The support of their javascript packages is painfully poor. They do not reply to issues; you have to nag them constantly before anything is done; when it is done, it takes forever for simple stuff. I am talking about bugs, not features! Also, the platform offers too much freedom in my opinion; the docs do not give good guidance on how one would create, for example, a content page like healthline etc.

I needed a headless CMS solution for a JAM-Stack. It gets this done, but it takes forever to build. You would probably be better of just adding a WP and have theme that kind of looks like your main site.

Inexperienced people can learn to use the platform quite quickly. If the modules have been well designed I can imagine that in the long run it can save a lot of time.

It lacks the flexibility to configure options and the diversity of capabilities that other platforms that have been on the market for longer, such as WordPress, have.

The ease to change the content on the fly and make it look relatively acceptable. I don't know if we are more productive because we are limited by the lack of some essential capabilities like inserting line breaks in text or easily resizing headers, more list styles, etc.

That's a damn good question. Only their cheap prices I think.

Our experience with their customer support / SDRs are horrible. Resistance right when they get to know that you're not in their Enterprise plan, wrong names when addressing people, not following up on deadlines, and horrible internationalization API. Their API is what any dev would consider very rigid to work with, their docs are horrible, and their customer support doesn't know anything about their own product / API, so there is no human help to get. Good luck to the next dev sitting and guessing how their API is supposed to work.

I mean their folder structure is kinda good, but that's also it

Nothing, it's been a terrible product for our business from the beginning.

It is absolutely rife with bugs. At this point the amount of development hours we've spent just trying to circumvent the bugs has cost our business countlessly.

It's supposed to help us create content in a much more seamless way with universal components. However, it doesn't seem to be able to do that.