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.
I like the idea a lot, but some features seem not well tested/documented
What do you like best about the product?
The live editor is the best for me. It makes content editing easy
What do you dislike about the product?
There is still a lot of documentation from the old version of storyblok. Also, would be nice to have an official type generation tool from the company.
Versioning/branching is missing, this makes two people working on the same space very difficult when changing bloks schemas
Versioning/branching is missing, this makes two people working on the same space very difficult when changing bloks schemas
What problems is the product solving and how is that benefiting you?
Easy editing content on landing pages, so clients don't depend on devs to do this
- Leave a Comment |
- Mark review as helpful
Easy to integrate CMS, with a lot of collaboration features
What do you like best about the product?
The live editor, it's easy to understand, the community support
What do you dislike about the product?
It's not flexible in terms of having global reusable data. the bloks return an Array even if the min and max is set to 1.
The migration of existing data into a new structure is only possible with the API and it's not user friendly.
The migration of existing data into a new structure is only possible with the API and it's not user friendly.
What problems is the product solving and how is that benefiting you?
Creating a structure for our data. Letting the stakeholder manage the content.
Dominik's review
What do you like best about the product?
it create structured data, which can be use byt any app, to render dynamic content.
What do you dislike about the product?
In our project we are missing kind of versioning of content (data created). Also it wound be fine if we somehow can deliver code for rendering particular content.
What problems is the product solving and how is that benefiting you?
It provide UI to create structured data, which are used in out product/application. We can dynamically change data/content which customer receive without any complicated release process.
Best CMS. Easy to manage
What do you like best about the product?
All your dreams are in one CMS. I came to Storyblok from Wordpress! What a change.
Versatile system. Rich with applications and functionalities. Easy to build and to update.
Versatile system. Rich with applications and functionalities. Easy to build and to update.
What do you dislike about the product?
Nothing so far. With as much as I try, all is good.
Like any system, you would need to invest time to learn it, but the learning curve is not high or long.
Like any system, you would need to invest time to learn it, but the learning curve is not high or long.
What problems is the product solving and how is that benefiting you?
Very easy to expand and reuse multiple content in different pages.
Eay to create new components.
Eay to create new components.
Front-end developer
What do you like best about the product?
Great tool. Like the real time component changes.
What do you dislike about the product?
Not so great tool. Don't like the real time component changes.
What problems is the product solving and how is that benefiting you?
Changes of data throughout the app
Outstanding and easy
What do you like best about the product?
i work on creating and publishing articles, sometimes i do website maintenance and i do all of these easily without any knowledge of coding .. just storyblok. great job guys
What do you dislike about the product?
sometimes i get logged out unnecessarily, although i understand this is for security reasons
What problems is the product solving and how is that benefiting you?
it provides ease and makes my writing and publishing faster compared to other mediums
Perfectible and sometimes even frustrating
What do you like best about the product?
- Easy to see what is being changed on a page
- Always have someone at the other end to help figure stuff out
- I use it everyday
- Always have someone at the other end to help figure stuff out
- I use it everyday
What do you dislike about the product?
- Search bar is improving (no more deleted letters when writing a search request)
- But I still can't find what I want all the time
- I have to be very precise and can't look for pages using simple keywords
- I can't just click on the link of the live version of the page and have to navigate through our website to find it again
- No tool to edit a page from front that takes you to back automatically (like Hubspot extension) - which experience wise was a great help
- But I still can't find what I want all the time
- I have to be very precise and can't look for pages using simple keywords
- I can't just click on the link of the live version of the page and have to navigate through our website to find it again
- No tool to edit a page from front that takes you to back automatically (like Hubspot extension) - which experience wise was a great help
What problems is the product solving and how is that benefiting you?
It gives us a back office interface to publish content online.
A Storyblok superfan
What do you like best about the product?
With Storyblok, it's incredibly easy to amend content on the site, everything is organised and with a well-set up site, almost no team training is required. It's also incredibly easy to integrate all of your core applications.
What do you dislike about the product?
I've not come across any downsides to Storyblok. I guess I wish we could integrate Bynder without having to upgrade.
What problems is the product solving and how is that benefiting you?
Storyblok allows us to quickly and easily create content for our website and allows us as an internal marketing team to manage the whole site without having to rely on developers.
Easily adaptable and scalable CMS solution
What do you like best about the product?
From my point of view, Storyblok provides quite a lot of potential for an easily customizable CMS solution. Integration via JS storyblok bridge is easy as well, if completely customized behaviour of the api is needed, an own connector can be implemented as well.
What do you dislike about the product?
While implementing Plugins (applications) for storyblok we stumbled upon how to manage settings for plugins.
Here it would be very helpful to have a starter project, which already provides the settings part.
Then it would be easier to start with plugins, which need additional settings.
Here it would be very helpful to have a starter project, which already provides the settings part.
Then it would be easier to start with plugins, which need additional settings.
What problems is the product solving and how is that benefiting you?
Storyblok provides a scalable, easily customizable CMS solution. We are using it in several MACH oriented contexts as the CMS solution and are mostly very satisfied.
Powerful and Flexible
What do you like best about the product?
You can achieve almost anything due to they way Storyblok gives you the data you need, collect that data in some flexible react framework (next.js) and you've got the foundations of a very smooth experience that you can tailor to those not interested in the code.
Once the code pieces are put together the speed to market is rapid - components can be create and slotted into place very quickly and can be visually checked through whichever release process you decide to follow before it hits your production system - all thanks to that very clever visual UI.
There is quite a bit of headscratching and effort that went into just understanding the best approach but once there it really is a flexible system that Storyblok can easily improve overtime; enough is there at the moment though to get going.
Once the code pieces are put together the speed to market is rapid - components can be create and slotted into place very quickly and can be visually checked through whichever release process you decide to follow before it hits your production system - all thanks to that very clever visual UI.
There is quite a bit of headscratching and effort that went into just understanding the best approach but once there it really is a flexible system that Storyblok can easily improve overtime; enough is there at the moment though to get going.
What do you dislike about the product?
There are definately quite a few improvement points to made however, especially with the developer experience but there are work arounds, you just might need another backend tool to achieve them.
- API limitation on resolving relations to a minimum of two levels
- API logic limitation, filter query which gives you logic can only be used on content and then, as above, only 2 levels
- Documentation on best practice setup to achieve more complex tasks (i.e. this is how you would build a breadcrumb or on-page navigation)
- Stories/templates that would inherit the limited component use from the parent Template or Story
- API rate limt seems a bit low (100 story fetch limit is too low)
- Webhooks trigger could be more granular, i.e. on a per story/template/folder level
- Bulk edits to components/reusable content (i.e. I want this component to appear here on these pages, not possible, create an external tool and use the management API)
- Component re-naming checking (say you give a component a name that the API uses and you want to change it? Be great to see what pages thats impacted without having to write a bespoke tool to check and update/publish)
- Another (test?) access level key would be useful in addition to draft/published (Test > UAT > Prod).
- Image Service could do with a little improvements, its a bit hit and miss and sometimes a little slow.
- Would be great to see an automated language translation option
- API limitation on resolving relations to a minimum of two levels
- API logic limitation, filter query which gives you logic can only be used on content and then, as above, only 2 levels
- Documentation on best practice setup to achieve more complex tasks (i.e. this is how you would build a breadcrumb or on-page navigation)
- Stories/templates that would inherit the limited component use from the parent Template or Story
- API rate limt seems a bit low (100 story fetch limit is too low)
- Webhooks trigger could be more granular, i.e. on a per story/template/folder level
- Bulk edits to components/reusable content (i.e. I want this component to appear here on these pages, not possible, create an external tool and use the management API)
- Component re-naming checking (say you give a component a name that the API uses and you want to change it? Be great to see what pages thats impacted without having to write a bespoke tool to check and update/publish)
- Another (test?) access level key would be useful in addition to draft/published (Test > UAT > Prod).
- Image Service could do with a little improvements, its a bit hit and miss and sometimes a little slow.
- Would be great to see an automated language translation option
What problems is the product solving and how is that benefiting you?
When moving away from an old web system to a headless CMS, we want our speed to market improved with rapid response times that we could use with any web stack we decide on and any webstack we want to migrate to in the future.
showing 61 - 70