Storyblok
StoryblokReviews from AWS customer
0 AWS reviews
-
5 star0
-
4 star0
-
3 star0
-
2 star0
-
1 star0
External reviews
521 reviews
from
External reviews are not included in the AWS star rating for the product.
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.
Great user experience for content editors
What do you like best about the product?
StoryBlok previews are great for allowing content editors to see what their pages are going to look like live in the browser. We have easily integrated it into our applications using the GraphQL endpoint. Also a big fan of the image processing power for use n the front end of our applications.
What do you dislike about the product?
The GraphQL response can sometimes feel a little bloated and clunky but that could be more to do with the way we have structured our data rather than how it is processed by StoryBlok
What problems is the product solving and how is that benefiting you?
StoryBlok is creating a really user friendly platform for our content editors to add pages and components to pages. The UI is slick and intuitive and the headless CMS allows us to use whatever frontend framework we wish to so that we can deliver super fast applications to the browser.
Storyblok is highly recommended
What do you like best about the product?
I recently had the opportunity to work with Storyblok for an ecommerce product MVP, and I must say that my experience with this platform has been nothing short of fantastic.
Developer-friendly GraphQL API:
The schema is well-documented and easy to understand, making it a breeze to query and manipulate data. I could retrieve exactly the data I needed without any over-fetching, which is crucial for optimizing performance.
Intuitive UI and UX:
Content editors and developers will appreciate the simplicity of the interface, making it easy for non-technical team members to manage content with minimal training. The real-time preview feature significantly streamlines the content creation process. You can see exactly how your content will appear on the live site as you edit it, which is a game-changer for developers working closely with content creators. This results in fewer iterations and a faster development cycle.
Content localization and versioning:
Storyblok's built-in support for content localization is a lifesaver, especially for ecommerce projects targeting international markets. The ability to manage content in multiple languages within the same project simplifies the process of creating a global presence. Furthermore, Storyblok's versioning system ensures that you can track changes, rollback if necessary, and maintain content consistency across various stages of development.
Developer-friendly GraphQL API:
The schema is well-documented and easy to understand, making it a breeze to query and manipulate data. I could retrieve exactly the data I needed without any over-fetching, which is crucial for optimizing performance.
Intuitive UI and UX:
Content editors and developers will appreciate the simplicity of the interface, making it easy for non-technical team members to manage content with minimal training. The real-time preview feature significantly streamlines the content creation process. You can see exactly how your content will appear on the live site as you edit it, which is a game-changer for developers working closely with content creators. This results in fewer iterations and a faster development cycle.
Content localization and versioning:
Storyblok's built-in support for content localization is a lifesaver, especially for ecommerce projects targeting international markets. The ability to manage content in multiple languages within the same project simplifies the process of creating a global presence. Furthermore, Storyblok's versioning system ensures that you can track changes, rollback if necessary, and maintain content consistency across various stages of development.
What do you dislike about the product?
The GraphQL API documentation is not always up-to-date and this can be improved.
What problems is the product solving and how is that benefiting you?
Storyblok simplifies content management for developers and non-technical team members. It streamlines the process of creating, editing, and organizing content, reducing the back-and-forth between developers and content creators.
Really interesting Headless CMS
What do you like best about the product?
- Pretty easy and accessible to use.
- The free community plan has enough features and space to use for a personal blog or website.
- The free community plan has enough features and space to use for a personal blog or website.
What do you dislike about the product?
- Sometimes the Richtext rendering is not optimal.
What problems is the product solving and how is that benefiting you?
I created a personal portfolio and blog website. Using Storyblok has helped me to organize and write all my blog posts while offering the freedom to implement my custom web design.
For example, in my home page I created a slider to show every project preview I made, then the single project slide would link to its dedicated blog post.
For example, in my home page I created a slider to show every project preview I made, then the single project slide would link to its dedicated blog post.
Fabulous
What do you like best about the product?
Block componentes definition and console simplicity
What do you dislike about the product?
Pricing is to high for workspace........
What problems is the product solving and how is that benefiting you?
Content administraton flexibility
Great application for us to use to design and run our website
What do you like best about the product?
Most helpful part of Storyblok is the layout and the ease at which we can navigate the back end of the website to make changes shown on the front end
What do you dislike about the product?
Sometimes can be tricky importing and uploading assets to the asseet library and then adding them onto a specific page
What problems is the product solving and how is that benefiting you?
We had issues with website layout and updates that this has now fixed for us
Storyblok: Seamless Integration, Superior Results
What do you like best about the product?
Storyblok excels due to its framework-agnostic approach, offering seamless integration with any preferred framework. Whenever I encountered challenges, the proactive Storyblok team was immediately available on Discord to guide me towards a solution. Even as a novice developer, I effortlessly incorporated it into a system tailored for both SvelteKit and Storyblok. I consistently choose Storyblok for my projects, and the positive feedback from clients reinforces this decision. Furthermore, Storyblok is rich in features, boasting an array of data types (bloks) and an expanding suite of integrations, particularly its exemplary image service, which has notably optimized the website sizes I work on. I highly recommend Storyblok for its adaptability, support, and robust feature set.
What do you dislike about the product?
I wish storyblok had a more visual approach to sharing blok-schemas across projects. Currently they offer a CLI but the entire approach is relatively hands-on. It's similar to copy and pasting files in a way, and I think this could be achieved with an inbuilt app-like approach of drag and drop.
What problems is the product solving and how is that benefiting you?
I aimed to develop a system reminiscent of platforms like Webflow, where options and components are visually driven yet steered by my unique code. Storyblok empowers me to design and replicate a template that seamlessly integrates into every client project. This grants clients the speed and efficiency akin to low-code builders. However, it also provides the flexibility to tailor any specific design or development need. With just the initial version of my system, I'm already thrilled with the outcomes. Achieving such results without Storyblok or spending months crafting a less satisfying experience would be inconceivable.
Works perfectly for code/no-code teams
What do you like best about the product?
Storyblok works perfectly for our small code/no-code team consisting of a developer and me, a Content Creator and Manager without coding skills.
When we founded our first startup 6 years ago, we started with a self-programmed website and CMS, but that was too time-consuming in the long run. After all, we wanted to advance our own software and not spend the time adjusting our CMS. We tried out different CMS again and again. And then, we found Storyblok and it works perfectly for us.
When we founded our first startup 6 years ago, we started with a self-programmed website and CMS, but that was too time-consuming in the long run. After all, we wanted to advance our own software and not spend the time adjusting our CMS. We tried out different CMS again and again. And then, we found Storyblok and it works perfectly for us.
What do you dislike about the product?
The one thing that's not ideal is the asset manager. We upload a lot of pictures for every landing page and every article. It's possible to add many pictures at once and that's great, but then we can't rename the files. In consequence, I do not find them when I want to add them to my page. The workaround is to upload the pictures one by one when working on a particular page.
What problems is the product solving and how is that benefiting you?
1. Rapid Landing Page Creation: The feature stands out the most for me it the fast landing page creation capability. Without writing a single line of code, you can craft captivating landing pages in a matter of minutes. You can easily duplicate content blocks from one page to another.
2. Multilingual Website Creation Made Simple: We can easily manage our content in different languages within the same interface without coding anything.
3. Tailwind UI Integration: Based on Storyblok, we built a beautiful website thanks to Tailwind Ui’s stunning design elements. That’s the moment, my developer came in ; )
2. Multilingual Website Creation Made Simple: We can easily manage our content in different languages within the same interface without coding anything.
3. Tailwind UI Integration: Based on Storyblok, we built a beautiful website thanks to Tailwind Ui’s stunning design elements. That’s the moment, my developer came in ; )
Headless CMS with great value for affordable price
What do you like best about the product?
Great preview feature that makes a difference comparing to other CMS platforms.
What do you dislike about the product?
Minor bugs. I can live with them as they not break the overall experience.
What problems is the product solving and how is that benefiting you?
When we were looking for a headless CMS solutions, there was nothing to compare with Storyblok reagarding flexibility, ease of use and the amazing preview feature that makes the introduction of new content much easier.
showing 171 - 180