Storyblok
StoryblokReviews from AWS customer
0 AWS reviews
-
5 star0
-
4 star0
-
3 star0
-
2 star0
-
1 star0
External reviews
521 reviews
from
External reviews are not included in the AWS star rating for the product.
Great experience for both devs and content editors
What do you like best about the product?
The reason Storyblok is my favourite CMS is that it has both a great dev experience as well as content editing experience without making sacrifices when it comes to either. Their support is great as well!
What do you dislike about the product?
Sometimes the tutorials for specific frameworks aren't perfect, but it's a minor issue. Other than that, no complaints here.
What problems is the product solving and how is that benefiting you?
Allowing for a great content editing experience for non-technical people while still allowing us a lot of flexibility with how we set up and code the frontend. The visual editor is awesome!
Easy to use content management system
What do you like best about the product?
Storyblok is extremely easy to use for both content manager and developers who will use their API to connect and get content programatically. After few minutes of setup and relatively short API integration time you can start using it.
What do you dislike about the product?
I faced only two simple issue while using it. First of them is, We had to switch to richtext to be able to use URLs instead of description. Second one is there is no document versioning. You can't update new document without changing document url.
What problems is the product solving and how is that benefiting you?
We have used Storyblok to create static web contents in our web and mobile app dashboard. We also use it for storing documents that needs to be accessed in app.
Game changing CMS for quick turnaround
What do you like best about the product?
The documentation and guides to get started with Storyblok is very concise. There were one or two innacuracies due to API changes in frontend frameworks but never enough that the I couldn't get the example working on my own setup. I appreciated the boilerplate code blocks that were often times a copy/paste for my purposes which saved a lot of time.
From there I was able to extend the examples to meet the demands of the project.
Having looked at other headless CMS's I was sold on Storyblok with their editing UI that connects to either a production application to serve the content or a local port for a dev server to allow for live reloading of application changes alongside live reloading of CMS data. The two combine create a game changing dev experience that allows for very rapid development. I was able to turnaround a first draft to demo in under two days. Easily got something working on day one.
From there I was able to extend the examples to meet the demands of the project.
Having looked at other headless CMS's I was sold on Storyblok with their editing UI that connects to either a production application to serve the content or a local port for a dev server to allow for live reloading of application changes alongside live reloading of CMS data. The two combine create a game changing dev experience that allows for very rapid development. I was able to turnaround a first draft to demo in under two days. Easily got something working on day one.
What do you dislike about the product?
On the technical side of there seems to be an issue with using the content editing UI alongside a local dev server while watching YouTube (maybe other streaming services affected as well). YouTube begins to lose connection / stutter. When I close the tab for Storyblok the video plays without issue.
This does not occur when connected to a production application so I suspect the editing UI slamming the local port causes some sort of DDos like scenerio that perhaps cripples the bandwidth. Not sure exactly but I've only tested with Chrome on Windows 11. Not sure if this affects other browsers.
This does not occur when connected to a production application so I suspect the editing UI slamming the local port causes some sort of DDos like scenerio that perhaps cripples the bandwidth. Not sure exactly but I've only tested with Chrome on Windows 11. Not sure if this affects other browsers.
What problems is the product solving and how is that benefiting you?
We needed a way to host content that can be utilized in multiple contexts. The simplest context is such that a non technical content creator can modify. The live reloading feature of the Storyblok editing UI allows for them to visually see their changes in realtime while reasonably change layouts and visual appearances.
Good headless CMS with potential for greatness
What do you like best about the product?
It's really easy to use, versatile and you can do a lot without writing a single line of code.
What do you dislike about the product?
There are some small but annoying glitches, such as Storyblok suddenly logging me out in the middle of something important.
What problems is the product solving and how is that benefiting you?
Storyblok makes my CMS work faster as it is intuitive, easy to use and bug-free.
Great headless CMS
What do you like best about the product?
It's a great CMS, easy to use. Very productive. Great free version, which is actually useable :)
What do you dislike about the product?
Don't now any. Maybe a simulationius preview of different breakpoints at once?
What problems is the product solving and how is that benefiting you?
Seperating content and development
Great editor functionalities and easy to use, set up for different languages can be improved
What do you like best about the product?
The user experience is very good, new editors can start working quickly without bigger introduction since the structure is really intuitive. Also in the backend there is a lot flexibility which allow us to reach different goal with minor effort.
What do you dislike about the product?
I find really complex the dimensions and they don't work as I would expect from a very good tool as Storyblok. For multilingual webites it's important to have a clear process how to work with the languages and this is not the case.
What problems is the product solving and how is that benefiting you?
We wanted to change to a headless CMS in order to improve the performance of our website with static pages, have much more flexibility introducing personalisation and A/B testing and also improve the editor experience.
Flawless developer experience - Cutting edge technologies & excellent support
What do you like best about the product?
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.
What do you dislike about the product?
On major upgrades or launches of new libraries, documentation and source code sometimes don´t match, but that´s just a minor issue.
What problems is the product solving and how is that benefiting you?
Providing an CMS with up-to-date APIs and technologies, supporting all our needs.
Easily and Fast Integrate Content into your Website
What do you like best about the product?
Easy to integrate on a website, flexibility for adapting the content to our needs.
What do you dislike about the product?
Documentation for more advanced details, is often hard to find. Often I find outdates docs first.
What problems is the product solving and how is that benefiting you?
It allows us to separate website development from content editing. As the devs, we can provide the components but do not need to spend time on the content. Before, we needed to have a back-and-forth when the content on the page needed to be updated. Like all other parts of our website, storyblok is headless, and this reduces energy consumption which should be a goal for all websites.
A good idea, but failed execution
What do you like best about the product?
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).
What do you dislike about the product?
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.
What problems is the product solving and how is that benefiting you?
Allowing non-techinical staff within my organization to customize marketing sites based on components developed by our frontend-engineering team.
Exceptionally user-friendly headless CMS
What do you like best about the product?
The preview feature is by far the platform's most impressive and helpful facet. But just as helpful are the drag-and-sort block reorganization, as well as the copy and paste features. We've reduced content population and new page creation by approximately 75% with these tools alone.
What do you dislike about the product?
One downside is that it's not open source. So if our team wants to suggest a feature enhancement, we have to work through Storyblok's support, as opposed to just developing it ourselves.
What problems is the product solving and how is that benefiting you?
A headless CMS that works with modern web frameworks and makes it easy for Marketing to own content. This allows us to develop highly optimized and secure websites for our clients, and makes it simple for our clients to manage the content themselves.
showing 191 - 200