Reviews from AWS Marketplace
0 AWS reviews
-
5 star0
-
4 star0
-
3 star0
-
2 star0
-
1 star0
External reviews
External reviews are not included in the AWS star rating for the product.
Headless CMS that really works for structured content
What do you like best about the product?
It's a no-nonsense headless cms with a great delivery API. Also it supports the types of nested content that supports structured content very well (like for producing website structure and slugs deep slugs).
What do you dislike about the product?
The tooling is extensive with SDKs for several frontend frameworks. But, at the time of writing some of them could require better documentation and structure.
What problems is the product solving and how is that benefiting you?
Using Storyblok as CMS for several websites and one content-based app.
- Leave a Comment |
- Mark review as helpful
Surprised!
What do you like best about the product?
Storyblok was directly intuitive. Very quickly the structure behind it could be understood.
What do you dislike about the product?
Instructions were not exactly easy to understand at the beginning. You might want to choose a flatter start here.
What problems is the product solving and how is that benefiting you?
Try another headless CMS. Flexibility was the decisive advantage here
Storyblok is a easy way to build your site.
What do you like best about the product?
- WYSIWYG preview, the preview is awesome.
- Custom data strucutre.
- Publish approval progress.
- Custom data strucutre.
- Publish approval progress.
What do you dislike about the product?
- Assets preview, can't the whole image in assets list (seems they have improve this in v2)
What problems is the product solving and how is that benefiting you?
Easily to build a static webpage, it's easy for engineering and content to work together.
Amazing user experience !
What do you like best about the product?
The live editor of Storyblok is awesome, every user, even non-technical people is very comfortable.
What do you dislike about the product?
This is a saas software, as it, you are tied to the pricing plan.
What problems is the product solving and how is that benefiting you?
Storyblok provides a very valuable headless CMS for JAMStack websites
Storyblok is changing the game
What do you like best about the product?
Storyblok makes it easier than ever to manage website content.
All of my clients have mentioned how easy it is for them to go in and manage their website content.
From a developer standpoint, Storyblok is excellent. They make it extremely simple to create new content blocks that can easily be implemented.
All of my clients have mentioned how easy it is for them to go in and manage their website content.
From a developer standpoint, Storyblok is excellent. They make it extremely simple to create new content blocks that can easily be implemented.
What do you dislike about the product?
I don't really have anything negative to say about Storyblok. The only thing I would ask from the Storyblok team is to add built-in Typescript type definition generation.
In the meantime, I created a npm package that does just that: https://www.npmjs.com/package/@brbndigital/storyblok
In the meantime, I created a npm package that does just that: https://www.npmjs.com/package/@brbndigital/storyblok
What problems is the product solving and how is that benefiting you?
Being able to set up a CMS in a matter of minutes and have it integrated with whatever project I'm working on quickly is a massive time saver.
Not only does it save me time in my development cycle, but it provides an easy-to-use interface to my clients so they can manage their own content without too much hand holding.
Not only does it save me time in my development cycle, but it provides an easy-to-use interface to my clients so they can manage their own content without too much hand holding.
Recommendations to others considering the product:
Over the last year, I've spent a lot of time researching and trying out different headless CMS services.
Storyblok is hands down the best one I've found.
Storyblok is hands down the best one I've found.
Easy to use CMS. Good documentation. Equally easy to use for developers as well as content team.
What do you like best about the product?
Easy to create components. Visual editor is good.
What do you dislike about the product?
Errors like 'You are not in edit mode' should be accompanied by link to documentation in which the error is elaborated.
What problems is the product solving and how is that benefiting you?
Support blogs within website that do not require interference from dev team.
Save yourself the hassle of updating your self-hosted CMS
What do you like best about the product?
Self-hosting a CMS for a website can be painful when it comes to regular maintenance tasks - applying security patches, updating the database, and adapting your custom backend code to changed APIs. Using Storyblok as your 'content repository' you can avoid this hassle and focus on your frontend code without worrying about future backend upgrades.
What do you dislike about the product?
Once your web project starts growing, you might soon reach a point where the feature set of the free 'Community' account doesn't cut it anymore. Going from 'free' to '90 Euros/month' ('Entry' plan) is not for the faint of heart.
What problems is the product solving and how is that benefiting you?
Website Content Management. No setup, no maintenance, and a powerful editing interface out-of-the-box. Plus it's really easy to build your own content editing components based on Vue.js
Very Satisfied
What do you like best about the product?
It was very easy to implement Storyblok in our Nuxt application. And also very easy to create content with the visual editor. Everyone is satisfied with the new CMS
What do you dislike about the product?
If i have to mention one thing, it would be that it isn't possible at the moment to filter published/unpublished stories. Which makes it hard to check where we have unpublished content.
What problems is the product solving and how is that benefiting you?
Before Storyblok we had our content in the code, so we needed software developers to update the content of the page. With storyblok it is much easier. The development team can concentrate on the big things.
Recommendations to others considering the product:
Try the free version and implement a full page of your website. So you can easy check if storyblok fits your needs.
One and only CMS for startups.
What do you like best about the product?
Flexibility in building what is currently desired.
What do you dislike about the product?
Buggy behaviour of editor resizing, fix it please :)
What problems is the product solving and how is that benefiting you?
It doesn't matter what kind of page you are currently building for your site, Storyblok can handle it all :)
A viable competitor to larger, more established headless CMS SaaS on the market
What do you like best about the product?
Our team has used Storyblok as a headless CMS solution for more than 2 years now.
After multiple projects, I find that the complexity of achieving certain features reduced dramatically – when compared to 2 years ago.
Looking back to when we first adopted Storyblok on a regular basis, I've seen the product improve both in editor and development experience — visual editor, bridge and asset manager.
Based on this I believe Storyblok's strong point is that their team listens to developer and customer feedback and uses that to continuously improve their product.
On a similar note, it's easy to get direct access to their development team when you contact support.
I am especially happy with the Image service and the GraphQL API (although this one isn't as clearly documented as its REST counterpart).
After multiple projects, I find that the complexity of achieving certain features reduced dramatically – when compared to 2 years ago.
Looking back to when we first adopted Storyblok on a regular basis, I've seen the product improve both in editor and development experience — visual editor, bridge and asset manager.
Based on this I believe Storyblok's strong point is that their team listens to developer and customer feedback and uses that to continuously improve their product.
On a similar note, it's easy to get direct access to their development team when you contact support.
I am especially happy with the Image service and the GraphQL API (although this one isn't as clearly documented as its REST counterpart).
What do you dislike about the product?
Creating user roles on spaces and managing granular permission for each role leaves a lot to be desired right now.
I'm also not a fan of their plugin/custom app development ecosystem forcing developers to use NuxtJS/Vue – although it's not as problematic now that they also provide their component library as a package.
Table fields could benefit from allowing rich text editors on cells instead of plain text fields.
Their CLI for the management API also doesn't parallelize requests.
Likely there's a reason behind it, but we found it slower than desirable for our needs to upload assets in bulk.
I'm also not a fan of their plugin/custom app development ecosystem forcing developers to use NuxtJS/Vue – although it's not as problematic now that they also provide their component library as a package.
Table fields could benefit from allowing rich text editors on cells instead of plain text fields.
Their CLI for the management API also doesn't parallelize requests.
Likely there's a reason behind it, but we found it slower than desirable for our needs to upload assets in bulk.
What problems is the product solving and how is that benefiting you?
We're using Storyblok as the content layer for multiple applications, mainly corporate websites.
For applications belonging to the same organization, we found it trivial to "containerize" all application configurations for each affiliate/branch using datasources.
For applications belonging to the same organization, we found it trivial to "containerize" all application configurations for each affiliate/branch using datasources.
Recommendations to others considering the product:
Always consider trying to reach their development team, either via support or by opening tickets on one of their Github repositories.
The API connectors are open source. If you need to build something they don't provide already, you could look into their tools code as a way to understand how to best make use of Storyblok's APIs
The API connectors are open source. If you need to build something they don't provide already, you could look into their tools code as a way to understand how to best make use of Storyblok's APIs
showing 301 - 310