Storyblok
StoryblokReviews from AWS customer
0 AWS reviews
-
5 star0
-
4 star0
-
3 star0
-
2 star0
-
1 star0
External reviews
535 reviews
from
External reviews are not included in the AWS star rating for the product.
Easy-to-Use Headless CMS
What do you like best about the product?
Super easy to navigate and organize your content. And you can have multiple spaces in case you want to keep different content projects separate.
What do you dislike about the product?
Don't dislike anything, but it definitely feels pretty basic for non-developers. Although I do love that it's usable by non-developers like me while providing additional functionality to people who understand code.
What problems is the product solving and how is that benefiting you?
Building the back end of a blog for a side project I'm working on with my developer friend.
Finally ! A headless CMS on which I can see and show components and content in live preview !
What do you like best about the product?
Storybook's Visual Editor allows you to set up a 'bridge' between the CMS and your frontend so that you can preview (live !) your work et your changes... in the CMS editor !
Honestly, I have searched, tried, and re-tried others CMS and... Storyblok is the one that fits the most to my needs.
Honestly, I have searched, tried, and re-tried others CMS and... Storyblok is the one that fits the most to my needs.
What do you dislike about the product?
For internationalization, Storyblok offers the possibility to add several languages, but you can't change the default one, called 'default'. I would rather have the option to set an existing language as the default language than having a default one corresponding to nothing but 'default'.
There are, however, workarounds and the Storyblok team keeps working on improvements.
There are, however, workarounds and the Storyblok team keeps working on improvements.
What problems is the product solving and how is that benefiting you?
Live preview of custom components is, to me, a must-have for my clients.
Storyblok is way more than a content management system
What do you like best about the product?
Visual editor, live preview of content
Intuitive in maintenance, nearly doesn't need any briefing for new people to understand how content is managed
Flexible -> implementation of new features is really easy
Inheritance logic for languages/countries
Intuitive in maintenance, nearly doesn't need any briefing for new people to understand how content is managed
Flexible -> implementation of new features is really easy
Inheritance logic for languages/countries
What do you dislike about the product?
Nothing. Suggestions of improvements are always recognized by Storyblok.
What problems is the product solving and how is that benefiting you?
We are using Storyblok not only for content, but also for promotions, redirects, shop configurations, merchandising and SEO stuff.
Modular system and visual editor enables us to build content twice as fast as before.
Modular system and visual editor enables us to build content twice as fast as before.
Recommendations to others considering the product:
Really easy, intuitive and flexible CMS. It is a lot of fun to work with.
Loving Storyblok Visual Editor and Developer Experience (DX)
What do you like best about the product?
I think the time and developer experience for setting a project from scratch with Storyblok and Next.js is lightning. Having built my entire portfolio with Next.js, Layer0 and Storyblok (https://rishi.app/), I know I chose the right CMS Provider 😄
What do you dislike about the product?
I think what Storyblok can improve upon is adding next, previous functionality to their GraphQL queries, but other than that all awesome.
What problems is the product solving and how is that benefiting you?
I think the benefit is instant publishing, unpublishing. As a tech writer, I feel that Storyblok has achieved this feat of at least getting people like me started instantly.
Storyblok can handle anything we throw at it. It's the most capable CMS we have ever used.
What do you like best about the product?
Storyblok allows us to create schemas without any limitations. Its flexibility is unmatched. We were able to create a massive block-based website and it had a solution to every requirement we had – from advanced editor permissions, to its own image optimization service.
What do you dislike about the product?
If I were to point something that's not great in Storyblok it would definitely be its dashboard. The UI (and, sometimes, the UX) could use a little work.
It could also be nice to have a "repeatable" field that could allow us to create a single-use schema (instead of having to create a new independent schema and using "block" with component whitelist).
It could also be nice to have a "repeatable" field that could allow us to create a single-use schema (instead of having to create a new independent schema and using "block" with component whitelist).
What problems is the product solving and how is that benefiting you?
We're building apps and websites that allow more flexibility and independence for the clients
Great SaaS for modern Websites and Apps
What do you like best about the product?
Easy to implement, great for complex projects with different teams and roles. Easy to set up multilanguage pages. Pricing is ok.
What do you dislike about the product?
There is nothing I do not like about this product. I use it for more than 15 Projects already, and it's an excellent fit for all my use cases until now.
What problems is the product solving and how is that benefiting you?
We create complex websites and mobile apps.
amazing
What do you like best about the product?
Storyblok is very easy to navigate and access. It is a handy tool. It is easy to get videos and download them.
What do you dislike about the product?
I don't dislike anything. It is an amazing program
What problems is the product solving and how is that benefiting you?
I am able to search and research various content for work and home.
Recommendations to others considering the product:
use it as often as possible
How a headless CMS should be built these days
What do you like best about the product?
The headless CMS offers great features out of the box. It is particularly noteworthy that the block-based approach offers the developer maximum flexibility - the unique visual editor helps the customer a lot to make use of this feature without any technical knowledge.
The ease of use when implementing Storyblok into any application developed in any language is remarkable. Storyblok is a perfect fit when working with a modern techstack, e.g. JAMstack (with any component-based frontend framework). It helps to develop fast, being able to customize as much as needed and deliver quickly. Even extending the functionality in the Storyblok backend UI is possible through field-types and apps.
The ease of use when implementing Storyblok into any application developed in any language is remarkable. Storyblok is a perfect fit when working with a modern techstack, e.g. JAMstack (with any component-based frontend framework). It helps to develop fast, being able to customize as much as needed and deliver quickly. Even extending the functionality in the Storyblok backend UI is possible through field-types and apps.
What do you dislike about the product?
Compared to other (headless) CMS it's hard to find criticism. The only thing which could have felt more intuitive for a beginner is the way to query the content delivery API - which does not follow default REST principles. But one get used to it quickly.
What problems is the product solving and how is that benefiting you?
Storyblok enables a lot of opportunities to solve all kind of different problems. At our digital agency we use Storyblok to create marketing and e-commerce websites as well as custom business applications. As we use VueJS (NuxtJS) to build most of the applications, the block-based approach helps us to structure our applications, even when the CMS is not actually used by our clients. We are able to quickly combine and nest all kind of developed components to build a blazing fast JAMstack webapp.
Recommendations to others considering the product:
I can recommend Storyblok to every company which wants to have a scalable, extendable and reliable solution. Best fit for any JAMstack application which needs a content management solution.
A good headless CMS
What do you like best about the product?
- Functioning system
- Simple interface
- Good development potential
- Good account and content overview
- Good support
- Simple interface
- Good development potential
- Good account and content overview
- Good support
What do you dislike about the product?
So far, only good experiences gathered
What problems is the product solving and how is that benefiting you?
Storyblok is used as our content management system. The following topics have been implemented so far:
- Mega menu
- SEO texts
- Text, image, and video elements
- Shop the look
- Mega menu
- SEO texts
- Text, image, and video elements
- Shop the look
Recommendations to others considering the product:
A very clear recommendation for Storyblok.
Happy so far, generally prefer open source solutions on principle, though.
What do you like best about the product?
The content model. It's simply unrivaled and what I always wished for.
- Every other CMS our there still wants me to assign specific named fields for a content type instead of letting me use blocks of well-defined structure in a hierarchical way within a content item.
- There are not only collections of types of content, but an actual hierarchy.
- Every other CMS our there still wants me to assign specific named fields for a content type instead of letting me use blocks of well-defined structure in a hierarchical way within a content item.
- There are not only collections of types of content, but an actual hierarchy.
What do you dislike about the product?
I wish there were more convenient ways to query *all* content items in a way that includes Caching.
The grapthQL API
- is not cached (as far as I know)
- does not let me query different content types at once (when searching for fields that all of them still may have in common)
The grapthQL API
- is not cached (as far as I know)
- does not let me query different content types at once (when searching for fields that all of them still may have in common)
What problems is the product solving and how is that benefiting you?
A typical corporate content thing.
showing 511 - 520