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.
Great headless cms that’s always improving
What do you like best about the product?
Live preview, support channels and helpful staff
What do you dislike about the product?
Setup can be a bit cumbersome, clear guidelines for different setups would be great
What problems is the product solving and how is that benefiting you?
Ease of use for the client and simple deployments means no crazy infrastructure setups.
- Leave a Comment |
- Mark review as helpful
Very powerful CMS
What do you like best about the product?
Easy to learn and use CMS, with an intuitive UI. A big plus is that you can reuse your well-structured content. Supports multiple integrations with a variety of APIs, including GraphQL.
What do you dislike about the product?
Documentation is not equally detailed. For example, the REST API is not as straightforward as GraphQL. I would love to have equal quality of documentation for all features.
What problems is the product solving and how is that benefiting you?
Storyblok helps me to manage my CMS needs entirely and don't have to rely on other solutions and services. Prices are also reasonable, including community licenses for developers.
Recommendations to others considering the product:
Storyblok has a Community license that is great to get used to the system.
Fast, reliable and flexible.
What do you like best about the product?
Storyblok is a very flexible and reliable service. The visual preview and image service are outstanding.
What do you dislike about the product?
The API documentation for complex queries is not very helpful.
What problems is the product solving and how is that benefiting you?
Complex data structures are effortless to create and, at the same time, straightforward to make understandable and usable for the client.
Storyblok
What do you like best about the product?
I love the visual editor as it is a great selling point when I was presenting this an option for the internal editors that will be using the tool. It is the only option I have found with such a feature.
What do you dislike about the product?
I love using the GraphQL API although the documentation is not as clear as the REST API documentation.
I would like to see direct integration with BitBucket for CI/CD rather than using a webhook that then relies on another service to integrate with BitBucket.
I would like to see direct integration with BitBucket for CI/CD rather than using a webhook that then relies on another service to integrate with BitBucket.
What problems is the product solving and how is that benefiting you?
Allowing a dynamic website that can change without constant developer involvement. I built the site with the Nuxt framework and it was much easier than I initially thought to integrate Storyblok CMS.
Flexible, intuitive and well thought-out platform hampered by a lack of support for the tricky bits
What do you like best about the product?
Storyblok's flexibility in creating content types and presenting them via the API is brilliant, intuitive, and very straightforward to implement. The interface is fast - very fast, and the incredible power of components and blocks makes for a genuinely superior client editing workflow. I was able to get the data out of the API and spin up a working frontend in no time.
What do you dislike about the product?
Migrating from another platform was outrageously simple and, in turn, an utter nightmare. Importing via CSV was super easy. Unfortunately, the documented methods for converting HTML to markdown, then markdown to rich text don't work out of the box. Although I managed to get half the process done (html to markdown), I was never able to make that final step to richtext - and with an esoteric request like this, I just wasn't able to get any support for the issue.
What problems is the product solving and how is that benefiting you?
Storyblok provides an intuitive and fast editing experience for my clients that allows me to set constraints on the elements they can use and modify but allows them the freedom to create content as needed.
It also frees me from the limitations of monolithic platforms, and provides an excellent API-first approach to front-end development.
It also frees me from the limitations of monolithic platforms, and provides an excellent API-first approach to front-end development.
A quick wrap-up on Storyblok, a headless CMS with a view.
What do you like best about the product?
Storyblok stands out by being easy to use. Whether a developer, a writer, or a marketeer, you will enjoy a simple yet efficient UX.
Since we are evaluating a headless cms connectivity to the front-end should be one of your concerns. There again, things run smooth regardless of the front-end, thanks to good plugins.
Since we are evaluating a headless cms connectivity to the front-end should be one of your concerns. There again, things run smooth regardless of the front-end, thanks to good plugins.
What do you dislike about the product?
Some, like me, might be missing a little more flexibility to create models, but there is enough in the app to make it work out of the box for most use cases.
What problems is the product solving and how is that benefiting you?
Storyblok allows us to get content across our projects. The set-up time and overhead per project are minimal, so we can concentrate on our business which is creating content.
Recommendations to others considering the product:
Storyblok is a perfect fit for marketeers and content writers. For heavy data management, there are other options.
One of the most powerful CMSes out there
What do you like best about the product?
The reusability and the design system that Storyblok boasts integrates itself seamlessly into our way of working and our codebase. We've created more than one site using the same library of components and now simply seek improvements to the way that we're working with these components - and the spaces that utilise them. We use Storyblok every day as part of our work, whether it's developing a new feature or just creating a funky new page to show off the art of the possible. It's been so easy to create new content on the site that we find ourselves - even as developers - making fake content pages just to show off the work we've done and what can be acheived with it.
What do you dislike about the product?
V2 fixed a lot of the quirks and problems that we'd previously noted. It's a much slicker experience. My least favourite part of Storyblok, however, is how the Releases app seems to be a bolt-on to the content creation process. There are still inherent bugs and quirks with getting it to slot nicely into our spaces. For our teams, it feels absolutely vital, so it'd be nice to see it get more of a focus.
What problems is the product solving and how is that benefiting you?
It encourages the creation of reusable components that can be inserted within each other. This aligns with our development principles and ensures that we are not making everything bespoke, saving us time and also allowing the content teams to experiment more with what's available to us. That in turn leaves us with less pressure to guide them design principles.
Recommendations to others considering the product:
Make sure you have the fundamentals of your framework locked in. It makes getting started a lot easier. Also, the Storyblok Discord is invaluable.
Since last summer i am using storyblok for my personal portfolio website
What do you like best about the product?
I like the excellent documentation and the easy way of receiving data from the backend
I use it with NuxtJS to get serverside rendering and to get a good SEO performance.
I use it with NuxtJS to get serverside rendering and to get a good SEO performance.
What do you dislike about the product?
I tried to use Storyblok as a backend for an App, but it doesn't work.
Maybe it's not intended to do such things with it. I would like to have a user registration system built inside.
It would be great if that is possible.
Maybe it's not intended to do such things with it. I would like to have a user registration system built inside.
It would be great if that is possible.
What problems is the product solving and how is that benefiting you?
I think the primary problem at my old portfolio site was that the changing of the content was to uncomfortably. With Storyblok i´m ten times faster i think
much better than a pure node
much better than a pure node
Great CMS with a fantastic live editor
What do you like best about the product?
The live editor makes content editor's lives happy as they can see a preview of their new page as they create or edit it in real time.
What do you dislike about the product?
The official plugin with Gatsby is a bit outdated and doesn't work with the new Gatsby image API.
What problems is the product solving and how is that benefiting you?
Easy for developers to create components for content editors to build new pages with. When a change is required on a page, no developer is required and the editor can do it themselves.
Recommendations to others considering the product:
If content editors would like a preview of their site while they are editing content, then Storyblok is the CMS you should choose
Decent service but with a couple gotchas
What do you like best about the product?
The API has a number of options for filtering and querying. It's fast and concise. GraphQL support is great too.
What do you dislike about the product?
Relationships in the API are poorly implemented and difficult to workaround. Even the GraphQL API was missing a relationship lookup aspect.
What problems is the product solving and how is that benefiting you?
We needed to deploy a powerful CMS for a multimedia platform. The benefits was the visual editor which is a godsend for newcomer content maintainers.
Recommendations to others considering the product:
Determine if it fits your use case and try working with the API before you commit.
showing 371 - 380