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.
The best CMS
What do you like best about the product?
Having all projects managed from one place is so easy now with Storyblok. You can easily use Storyblok for all platforms that you need (web: vue, angular ... mobile) in a very easy way. Getting data is so easy.
What do you dislike about the product?
Once when you start to use Storyblok it’s easy and fast. In my opinion, pricing is probably expensive for the start but in comparison to others, it's still cheaper. But once when you start using it you can check partner benefits and becoming a partner is probably the best option.
What problems is the product solving and how is that benefiting you?
Storyblok solves problems with API Content Delivery. Hosting Images on CDN is also one great benefit. Also preview of your work in StoryBlok works great and you can realtime check your work.
- Leave a Comment |
- Mark review as helpful
Excellent and Unique CMS Product
What do you like best about the product?
- Visual preview of changes directly in the editor
- Ability to edit/drag and drop within the live preview
- GraphQL endpoints
- All the major functionality works as expected
- Ability to edit/drag and drop within the live preview
- GraphQL endpoints
- All the major functionality works as expected
What do you dislike about the product?
- Not quite as refined as some long-standing CMS products (although hopefully much of this is addressed in v2 in beta)
- Would like to see improvements in the Asset management
- User permissions and roles needs more control
- Would like to see improvements in the Asset management
- User permissions and roles needs more control
What problems is the product solving and how is that benefiting you?
We are working to solve the inability of our content writers and marketers to make changes to our sites with less developer interaction and reduce the turnaround time. This product is helping deliver this goal.
Recommendations to others considering the product:
Try out the live editor functionality, I haven't seen anything similar elsewhere.
Great Headless CMS
What do you like best about the product?
The integrated visual editor that makes content editing very easy.
What do you dislike about the product?
The richtext editor is partially improvable.
What problems is the product solving and how is that benefiting you?
You can easily and flexibly implement your own ideas about how a website can be edited.
Recommendations to others considering the product:
---
review for storyblok
What do you like best about the product?
component-based
manage assets
multiple users
draft/published stages
manage assets
multiple users
draft/published stages
What do you dislike about the product?
no synced blocks
no asset version control
nested component structure sometimes can be time-consuming to update
no asset version control
nested component structure sometimes can be time-consuming to update
What problems is the product solving and how is that benefiting you?
company website
non-developer coworkers can learn using it easily
non-developer coworkers can learn using it easily
Recommendations to others considering the product:
implement asset version control, asset optimization, sync content block
Great product, great staff, great choice for a headless CMS
What do you like best about the product?
Super easy to add in to any existing next.js project. Great support when something goes wrong. Lots of features being added in the years we have been using it.
What do you dislike about the product?
It has got a lot better over the years we have been using it; however it would be nice to have support for more generic sitewide options pages.
What problems is the product solving and how is that benefiting you?
Mostly next.js applications needing a headless CMS
A very useful and customizable tool for your tech stack
What do you like best about the product?
The ability to drag and drop content blocks with complex layouts in the visual editor saves a huge amount of time compared to HTML and other forms of manual coding these blocks. Plus, the ability to reuse these components across pages in order to retain marketing guidelines and brand consistency is huge for our marketing team members, who can all work these separately while remaining a cohesive release.
What do you dislike about the product?
Sometimes the interface can be a little glitchy. For example at certain browser sizes the HTML editor doesn't scroll properly and can be a bit of a nuisance. There are just some quirky things with the editors that take getting used to, but ultimately these are not huge deals and can be overcome for the advantages that Storyblok offers.
What problems is the product solving and how is that benefiting you?
We moved nearly our entire resource center from a locally hosted site into Storyblok, including solution briefs, video pages, and blogs. The move has given our whole team more flexibility and responsiveness when creating new content or updating old content. The ability to have nearly anyone on the team make edits or publish content has saved a lot of time, and we are sure that our brand guidelines will be met because of the modules we have in place and the ability to reuse those components.
Recommendations to others considering the product:
Work with their onboarding team to ensure your set up is ideal as possible for your use case.
The best headless CMS in existence.
What do you like best about the product?
What sets Storyblok apart from anything out there, is the ability to have a true data hierarchy, most headless content management systems lack this ability giving you data in a flat data structure. Not everyone is running a simple blog and Storyblok understands that, so they provide us with the ability to structure our stories in the way we want which is extremely powerful.
What do you dislike about the product?
I think that Storyblok could benefit from having tooling to manage stories across spaces, we have several spaces which correspond to different environments within our infrastructure and moving stories from one space to another as well as getting components copied over is a manual task via MAPI.
What problems is the product solving and how is that benefiting you?
Storyblok allows us to quickly push our marketing landers without the need for developer interaction, so our developers can focus on making new components while content managers focus on creating stories.
Recommendations to others considering the product:
Jump right in and give it a shot, there isn't anything out there that comes close.
Storyblok - a great headless CMS
What do you like best about the product?
The main thing would be the visual editor and also how easy it is to develop own blocks.
What do you dislike about the product?
Sometimes when a page has many blocks it can become a little bit cluttered to navigate with the visual editor.
What problems is the product solving and how is that benefiting you?
The main problem I am solving is offering great customixability and ability the client to manage their website by themselves.
Ultimate headless CMS!
What do you like best about the product?
Storyblok brings modularity, easy-to-use admin UI and clean API (rest/graphql). Storyblok stands out from the rest of the products with its page preview feature. As you change your content, you see rendered page preview instantly. I also enjoy how easy it's to add localizations and consume that content via API. Another strong point is the ability to extend admin UI by adding your custom plugins/field types.
What do you dislike about the product?
Storyblok being a SAAS product, your content is stored in the cloud. It might be tricky to maintain a full backup of your content. Pricing might also grow if you want all the features and have lots of CMS users.
What problems is the product solving and how is that benefiting you?
We saved development time which would be required if we wrote a content management system from scratch. Adding fields, changing structure is effortless compared to other solutions where you need to manage database migrations.
Recommendations to others considering the product:
If you are looking for headless CMS to manage your content, definitely put Storyblok on a short list
Best CMS for Developers and Customers
What do you like best about the product?
The side-by-side Preview within the CMS is awesome and unique in the HeadlessCMS space yet - and the UI is nice and clean.
The flexibility to configure and build my content-bloks directly in the CMS allows me, and most importantly my design/pm colleagues, to build almost anything.
The flexibility to configure and build my content-bloks directly in the CMS allows me, and most importantly my design/pm colleagues, to build almost anything.
What do you dislike about the product?
Depending on the Framework you are using, the setup isn't that self-explanatory or documented well. I'm still struggling with getting the Preview-Mode in Next.js to work.
If you add a link field within a blok, you need to add a separate field for the link-target to set with. Additionally, the links delivered within the Content-Delivery-API are quite hard to use as you need to use the property "cached_link" (the other property is always empty) and be sure to add a slash at the beginning (sometimes) when using as relative links.
If you add a link field within a blok, you need to add a separate field for the link-target to set with. Additionally, the links delivered within the Content-Delivery-API are quite hard to use as you need to use the property "cached_link" (the other property is always empty) and be sure to add a slash at the beginning (sometimes) when using as relative links.
What problems is the product solving and how is that benefiting you?
No more patching, manually updating and hosting of a CMS-Software.
A lot of work can already be done by non-development people, by building the Elements (bloks) directly in the CMS.
Flexibility to use with whatever Framework/Technology I want to
A lot of work can already be done by non-development people, by building the Elements (bloks) directly in the CMS.
Flexibility to use with whatever Framework/Technology I want to
showing 331 - 340