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.
Storyblok – A Flexible and Developer-Friendly Headless CMS
What do you like best about the product?
Visual Editor: The real-time visual editor makes it easy for non-technical users to manage and preview content.
Component-Based Approach: Content is structured in reusable blocks, which provides flexibility and consistency across pages.
Headless Architecture: Integrates seamlessly with modern frameworks (Next.js, Nuxt.js, React, Vue, etc.), enabling full control over frontend.
Collaboration Features: Roles, workflows, and approval processes make it practical for teams.
API-First: Fast, reliable APIs with GraphQL and REST support for versatile data access.
Good Documentation & Community: Well-maintained docs and an active developer ecosystem.
Component-Based Approach: Content is structured in reusable blocks, which provides flexibility and consistency across pages.
Headless Architecture: Integrates seamlessly with modern frameworks (Next.js, Nuxt.js, React, Vue, etc.), enabling full control over frontend.
Collaboration Features: Roles, workflows, and approval processes make it practical for teams.
API-First: Fast, reliable APIs with GraphQL and REST support for versatile data access.
Good Documentation & Community: Well-maintained docs and an active developer ecosystem.
What do you dislike about the product?
Learning Curve: The component-based setup can be confusing for newcomers and requires upfront planning.
Pricing Model: Costs can grow quickly depending on number of users and projects.
Complex Configurations: Setting up roles, workflows, and custom fields may feel overwhelming at first.
Performance at Scale: While generally fast, very large content models can introduce latency if not optimized.
Limited Built-in Marketing Tools: Compared to traditional CMSs, features like A/B testing, personalization, and SEO tooling are more basic or require third-party integration.
Pricing Model: Costs can grow quickly depending on number of users and projects.
Complex Configurations: Setting up roles, workflows, and custom fields may feel overwhelming at first.
Performance at Scale: While generally fast, very large content models can introduce latency if not optimized.
Limited Built-in Marketing Tools: Compared to traditional CMSs, features like A/B testing, personalization, and SEO tooling are more basic or require third-party integration.
What problems is the product solving and how is that benefiting you?
Storyblok has been solving several challenges for us around content management and delivery. As a headless CMS, it allows us to centralize content in one place and reuse it across multiple channels, such as websites, mobile apps, and other digital platforms. This has greatly reduced duplication of work and made our content strategy more consistent.
One of the biggest benefits is the visual editor, which empowers non-technical users to create and update content without depending on developers. This speeds up time to market for new pages and campaigns, while freeing developers to focus on building frontend features instead of managing copy changes. The component-based structure also ensures reusability and consistency, helping us maintain a cohesive brand experience.
On top of that, Storyblok’s workflows, roles, and versioning features have improved collaboration between teams, making it easier to manage approvals and avoid conflicts. Its API-first approach also keeps our setup future-proof, letting us integrate with modern frameworks and adapt to new technologies without redoing our content base.
Overall, Storyblok helps us work more efficiently, improves collaboration between technical and business teams, and gives us the flexibility to scale and evolve our digital experiences as needed.
One of the biggest benefits is the visual editor, which empowers non-technical users to create and update content without depending on developers. This speeds up time to market for new pages and campaigns, while freeing developers to focus on building frontend features instead of managing copy changes. The component-based structure also ensures reusability and consistency, helping us maintain a cohesive brand experience.
On top of that, Storyblok’s workflows, roles, and versioning features have improved collaboration between teams, making it easier to manage approvals and avoid conflicts. Its API-first approach also keeps our setup future-proof, letting us integrate with modern frameworks and adapt to new technologies without redoing our content base.
Overall, Storyblok helps us work more efficiently, improves collaboration between technical and business teams, and gives us the flexibility to scale and evolve our digital experiences as needed.
Gets the job done, but not ideal for non-technical users
What do you like best about the product?
I will preface by saying I'm not a developer or a designer. My company used an agency to design and develop our website, and all I do is content creation, copy, etc. So I can only speak about those features of Storyblok. I like working with blocks, the visual editor, and content that is logically ordered and organized. I'd say it's pretty flexible and allows for as much simplicity or complexity as you require. All in all, I'd say I can work quickly and intuitively with Storyblok, now that I'm familiar with it.
What do you dislike about the product?
There is definitely a learning curve, and the pricing can get very expensive for additional features. While I love it when it's working, the visual editor has been buggy. Other small issues have arisen over the years and at times the Storyblok team has been unhelpful and unresponsive.
What problems is the product solving and how is that benefiting you?
When redesigning our commercial website and documentation, we wanted an option that would make it easy for non-technical roles, like our sales and marketing teams, to update content.
Storyblok. A great platform for content designers.
What do you like best about the product?
After working closely with UX and our development team, we have created a Storyblok platform that allows fast and efficient content development. The reusable bloks make it easy to create consistent, structured content that looks great and is also accessible.
What do you dislike about the product?
We currently have a 15 minute period to wait for the cache to clear. This isn't ideal when we are making small updates or working on developing a page.
What problems is the product solving and how is that benefiting you?
Prior to Storyblok we were using a CMS that was really beginning to show it's age. We had to hand crank the HTML on pages just to allow us to display content in specific ways. The process was slow and time consuming. Using Storyblok we can now create content much more efficiently. We have a library of standardised components that we can use, which helps us create content quickly and consistently. The final product is good looking, accessible content that works on all platforms.
Why i still make use of Storyblok amidst other Headless CMS
What do you like best about the product?
What I enjoy most about Storyblok is how it enables a seamless workflow between developers and content editors, overall combines a flexible API-driven backend with an intuitive, real-time editing experience.
What do you dislike about the product?
What I dislike about Storyblok is that the learning curve can feel steep at first, and the pricing for advanced features may be high for smaller projects.
What problems is the product solving and how is that benefiting you?
since storyblok is in the business of solving the problem of bridging the gap between developers and content teams by providing a flexible headless CMS with a visual editor, i benefit a lot from this as a content provider/writer as this speeds up content updates and does this smoothly.
An absolute breeze, developing our new website with Storyblok has made us so efficient
What do you like best about the product?
The modularity and the customise with custom blok types and data sources, this has made developing our website feel bespoke without wrestling it any systems.
Customer support was there along the way to help us, they were friendly and helpful.
As for our marketing team, they have found using storyblok so easy, they are able to build pages without our assistance and frequently make updates to the site now.
Implementing new features to our website has never been so easy.
Customer support was there along the way to help us, they were friendly and helpful.
As for our marketing team, they have found using storyblok so easy, they are able to build pages without our assistance and frequently make updates to the site now.
Implementing new features to our website has never been so easy.
What do you dislike about the product?
The initial integration with Nextjs was a bit of a headache as there wasn't much documentation or answers online, I think this is due to the more recent adoption of newer version of nextjs.
We did however eventually get everything working. I look forward to furture version of storyblok, which I think they have already released, but we have yet to implement.
We did however eventually get everything working. I look forward to furture version of storyblok, which I think they have already released, but we have yet to implement.
What problems is the product solving and how is that benefiting you?
Allowing us to easily build our website in a structured way, making reusable components to build our website effectively and easy to maintain.
The all in one feel of the CMS is also great, serving up our assets optimised, it's great for our developers as they can easily get to grips with the system.
The all in one feel of the CMS is also great, serving up our assets optimised, it's great for our developers as they can easily get to grips with the system.
Great product for product managers with no coding competencies
What do you like best about the product?
Easy to use, great UI, lots of features !
What do you dislike about the product?
May not be the most efficient if you manage a large number of text boxes
What problems is the product solving and how is that benefiting you?
As a product manager, I need to update text on our pltaform and I can't code it myself, and we don't want to spend development budget on it as we have higher priority tasks.
Easy to use, for dev and end users!
What do you like best about the product?
Their UI is super intuitive, and easy to use. The docs for getting everything set up are spot on. We use this across our company site and usage is growing! We recently utilised the API to setup 1000's of templated pages proving how well the integration works
What do you dislike about the product?
We're currently investigating slowness which may or may not be related to Storyblok API requests in our NextJS application.
What problems is the product solving and how is that benefiting you?
Allowing marketing team members to quickly set up new pages without dev requirements
Very good experience, great UX
What do you like best about the product?
easy to use, easy to find features, it's easy for devs to set up new sections
What do you dislike about the product?
minor usability details like navigating between pages or how i need to reload the page for the new updates to show
What problems is the product solving and how is that benefiting you?
Collaboration between dev and marketing
Marketing
What do you like best about the product?
Its easy to use and you can see how it will look like while you are working
What do you dislike about the product?
the first training, but when you understand it is easy to use
What problems is the product solving and how is that benefiting you?
its fast and we can update multiple market's at the same time
My Persanal exerience with storyblok and how it helped my organisation solve content mangement
What do you like best about the product?
Right of the top of my head , i would say it being an API first platform , which made it really easy to integrate with frameworks like react and next. js for me as a Javascript software developer , it was a really great tool as opposed to what i and my team had been using before hand
What do you dislike about the product?
i'd say what i dislike about storyblok is that it may come with a more difficult learning curve for non-technical editors . in my experience onboarding other stakeholders onto the platform and explaining the content models was quite a pain .
What problems is the product solving and how is that benefiting you?
it solves the problem of allowing non technical and technical stakeholders , manage and distribute content effectively with little to no friction. for me its been great as once i setup alot of the heavy lifting the handoff process becomes seamless .
showing 11 - 20