Reviews from AWS customer
0 AWS reviews
-
5 star0
-
4 star0
-
3 star0
-
2 star0
-
1 star0
External reviews
482 reviews
from
External reviews are not included in the AWS star rating for the product.
Pleasant Headless CMS
What do you like best about the product?
I love the UI interface which allows ease of use for content creators.
Project setup for major frameworks is also fast.
There is a lot of content and community support for Storyblok so as a developer and user I'm pleased to find all the required knowledge on their dedicateda page.
Most of functionality can be done by my code so it's easy to integrate with other services.
My current company has a partner program and the contact with customer support is very good.
Project setup for major frameworks is also fast.
There is a lot of content and community support for Storyblok so as a developer and user I'm pleased to find all the required knowledge on their dedicateda page.
Most of functionality can be done by my code so it's easy to integrate with other services.
My current company has a partner program and the contact with customer support is very good.
What do you dislike about the product?
I worked with different CMS in my current possition, the functionlaity I lack the most is multiple spaces/environments for the content.
I wish there was a possibility to work on a content in dedicated space without fear of overriding the production content (an copy of content which can be modified for campaign purposes).
I wish there was a possibility to work on a content in dedicated space without fear of overriding the production content (an copy of content which can be modified for campaign purposes).
What problems is the product solving and how is that benefiting you?
It really simplifies the work with customer content, preparing pages from existing components speeds up the work as no developer support is required.
Easy to integrate, easy to use, live editor is a big plus
What do you like best about the product?
Storyblok is a big win for our team! The live editor is great for real-time feedback on your changes — it's super intuitive and easy to use, and setting it up was straightforward for its integration with our React app.
After one of our developers implements it, our marketing team can now handle the app announcements (every three weeks) and updates on their own, not blocking developer and QA times for review anymore. The multilingual support looks great and will be easy to add in the future.
After one of our developers implements it, our marketing team can now handle the app announcements (every three weeks) and updates on their own, not blocking developer and QA times for review anymore. The multilingual support looks great and will be easy to add in the future.
What do you dislike about the product?
We haven't encountered any issues so far, but our use case is pretty basic.
What problems is the product solving and how is that benefiting you?
Before for marketing announcement we had to do a dev ticket for an hardcoded implementation in the app. The ticket was taking dev time, and had to be reviewed by our QA. By now using Storyblok the marketing content is fully managed by the marketing team. They can handle the message and do the QA (or review in their case) of the content themselves and publish it whenever they want. It also means we don't have to rely as developer, on a prod release to display the latest content. All the dev had to do after setting up Storyblok was to transform the content component in the app to interact with Storyblok instead of having hardcoded data passed to ti.
Storyblok has been a great experience for me; it's a flexible and easy-to-use CMS
What do you like best about the product?
How flexible it is and how easy it makes content management for both developers and content teams.
What do you dislike about the product?
We have encountered some "Too Many Requests" (Error 429) issues. Additionally, in the Data Sources, it's not possible to select the key instead of the value to save a property.
What problems is the product solving and how is that benefiting you?
A customizable Headless CMS components
I highly recommend Storyblok
What do you like best about the product?
My web design and marketing company uses Storyblok in the majority of our projects, and it's our first choice when recommending a CMS to clients.
The combination of a good REST/GraphQL API, good integration with client-side frameworks (e.g. Astro, Nuxt), and a fairly decent graphical editor results in us being able to rapidly integrate it into new projects.
I was recently able to get a small marketing website for a client up and running within a few weeks using Storyblok and Astro. An equivalent with a different CMS (e.g. WordPress) would have had a lot more friction.
I haven't had very many interactions with their customer support team, but the two times I spoke to them, they understood the issue I was talking about quickly, and got back to me with a resolution almost immediately.
The combination of a good REST/GraphQL API, good integration with client-side frameworks (e.g. Astro, Nuxt), and a fairly decent graphical editor results in us being able to rapidly integrate it into new projects.
I was recently able to get a small marketing website for a client up and running within a few weeks using Storyblok and Astro. An equivalent with a different CMS (e.g. WordPress) would have had a lot more friction.
I haven't had very many interactions with their customer support team, but the two times I spoke to them, they understood the issue I was talking about quickly, and got back to me with a resolution almost immediately.
What do you dislike about the product?
My main reservation with Storyblok is that, as this is closed-source SaaS, our sites have a hard dependency on it, and we wouldn't be able to move to self-hosting should Storyblok's parent company shut down, or them alter the software in a way we disliked.
I would also prefer if it was easier to integrate our post schema into version control, or to lock down specific blok configurations so they couldn't be modified from the UI.
Also, I'd love a dark mode option in the CMS's UI.
I would also prefer if it was easier to integrate our post schema into version control, or to lock down specific blok configurations so they couldn't be modified from the UI.
Also, I'd love a dark mode option in the CMS's UI.
What problems is the product solving and how is that benefiting you?
We use Storyblok primarily as a headless CMS for powering websites. It allows us to get new websites up and running quickly and relatively easily, and offers a good experience for managing content.
Fantastic headless CMS
What do you like best about the product?
I love the flexibility, intuitive layout, and ease of use of CMS. Deployments work seamlessly, the editing and previewing experience is great. As a heavy user, one of my favorite features is the command bar search.
What do you dislike about the product?
Sometimes loading pages inside the CMS can be a bit slow and when saving changes the preview is not always automatically updated so I need to refresh the window to see the latest changes.
What problems is the product solving and how is that benefiting you?
Storyblok makes it easy for us to manage all our (multi-lingual) website content.
Learning curve for a new developer
What do you like best about the product?
The fact that I can create easy to use bloks for my marketing and design teams to use.
What do you dislike about the product?
There is a large learning curve when it comes to connecting components through Vue, however once this is mastered the platform is convenient.
What problems is the product solving and how is that benefiting you?
Storyblok benefits my team by allowing the marketing team to adjust the website without needing to consult me first.
Super flexible and easy to use!
What do you like best about the product?
In my opinion, Storyblok is an incredibly flexible and user-friendly CMS that is perfect for teams who want to manage content without hassle and with a lot of freedom. The CMS offers us as a company an incredibly intuitive experience, where you can make changes directly and immediately see the result, which greatly speeds up and simplifies the entire content management process. Setting it up and getting started is smooth and without much hassle, allowing even new teams to quickly get to work with it. When help is needed, we can easily reach the support team, which is particularly nice. We use Storyblok every day, and when you compare it to a standard CMS, this is really the better work.
What do you dislike about the product?
In my opinion, there are a few points that work less pleasantly. The visual editor can sometimes load slowly, especially with larger projects, which makes real-time editing a bit less smooth. Also, some integrations are somewhat complex, requiring you to regularly seek the help of a developer. Furthermore, it can become costly if you want to add extra features or plugins, making it less attractive for smaller organizations with a limited budget. But overall, I would definitely recommend Storyblok.
What problems is the product solving and how is that benefiting you?
For me, Storyblok solves common content management challenges that are often time-consuming and frustrating with other CMS systems. With the visual editor, I can see directly how my changes look, which greatly helps to save time and get approvals faster. The fact that I'm not tied to a specific platform or limited in how I deploy content makes it possible to push everything from one central place to multiple channels, such as a website, app, or even other devices. This is ideal when I'm working on projects that need to be used in different ways.
Additionally, I'm no longer busy rebuilding everything; by setting up components once, I can easily create new content that is consistent in style and structure. What is also very nice is that I can easily make Storyblok work with other systems I already use, so I don't waste time on complicated integrations.
And perhaps the biggest advantage for me is the technical flexibility that Storyblok offers. Because it is API-driven, I can work with any front-end framework I want, without being tied to a specific setup or structure.
Additionally, I'm no longer busy rebuilding everything; by setting up components once, I can easily create new content that is consistent in style and structure. What is also very nice is that I can easily make Storyblok work with other systems I already use, so I don't waste time on complicated integrations.
And perhaps the biggest advantage for me is the technical flexibility that Storyblok offers. Because it is API-driven, I can work with any front-end framework I want, without being tied to a specific setup or structure.
A Game-Changing Headless CMS for Modern Web Development
What do you like best about the product?
As a digital agency transitioning from TYPO3, what we appreciate most about Storyblok is its innovative approach to content management through reusable blocks. The visual editor stands out as a true game-changer, offering an intuitive interface that makes content management accessible even for non-technical users. Coming from TYPO3, we've found that client onboarding is significantly smoother with Storyblok, as the learning curve is much gentler. The flexibility in creating and managing layouts is exceptional, and the straightforward setup process allows us to get projects up and running quickly. Being an Austrian company like us adds a nice touch of familiarity, but more importantly, their understanding of European market needs is evident in their product design.
What do you dislike about the product?
The main pain point we've encountered with Storyblok is their pricing structure. The stark contrast between the free community tier and the entry-level paid plan creates a challenging decision point for smaller projects. This pricing gap can make it difficult to justify the transition for smaller clients or projects that need just a bit more than what the community tier offers but aren't quite ready for the full investment in the entry tier. A more gradual pricing scale would make it easier to scale with client needs and project requirements.
What problems is the product solving and how is that benefiting you?
As a digital agency specializing in creating custom websites and web applications, Storyblok solves several critical pain points in our content management workflow. The headless architecture perfectly aligns with our tech stack of Nuxt and Vue.js, allowing us to build modern, high-performance websites while giving our clients an intuitive way to manage their content. The visual editor bridges the gap between developers and content editors - something that was particularly challenging with TYPO3. This means our clients can actually see their content changes in real-time, significantly reducing the back-and-forth communication and revision cycles. The nested block concept allows us to create flexible, reusable components that maintain consistency across pages while giving clients the freedom to create unique pages without requiring developer intervention.
good experience
What do you like best about the product?
The ease to change and edit the design of my pages in the design view.
What do you dislike about the product?
It is difficult to configure the Enriched Text field so that it respects the styles, perhaps a more in-depth explanation of how to do it or a tutorial could help.
What problems is the product solving and how is that benefiting you?
I give freedom over the design while I have at hand a platform that allows me to manage my content and give flexibility to the design with ease.
A powerful and intuitive CMS designed to meet the needs of both customers and developers.
What do you like best about the product?
That it is easy to set up and headless. Also the contact with them has ben very personal.
We are migrating 5 websites and it's been going very smooth.
We are migrating 5 websites and it's been going very smooth.
What do you dislike about the product?
There is no clear cut way on how to support multiple websites in a single space.
We had to do some research for that. I would have loved some advice on that from the start.
We had to do some research for that. I would have loved some advice on that from the start.
What problems is the product solving and how is that benefiting you?
It solves content management in a good way. The UI is good and well thought out which makes in user friendly.
And a from a developer experience. We had pages up and running within a day because of their open source tooling for nextJS.
And a from a developer experience. We had pages up and running within a day because of their open source tooling for nextJS.
showing 51 - 60