Storyblok
StoryblokReviews from AWS customer
0 AWS reviews
-
5 star0
-
4 star0
-
3 star0
-
2 star0
-
1 star0
External reviews
535 reviews
from
External reviews are not included in the AWS star rating for the product.
State of the art, probably best in class (headless) content management system (CMS)
What do you like best about the product?
An easy and fast way to deploy a CMS to small, medium and large companies. Very intuitive backend for all the content work and an amazing improvement in the page speed.
What do you dislike about the product?
There are no worries, The system is running smoothly, not one outtake in more then 3 years and the further development still promises a lot for the future.
What problems is the product solving and how is that benefiting you?
Bulding up a website in a very short time. To scale the workload was an easy task.
Recommendations to others considering the product:
The combination of an outstanding product with a highly passionated and professional team guarantees a successful implementation. Convince yourself in the free test.
A gem that bridges the gap between developer convenience and end user experience
What do you like best about the product?
- Storyblok can connect to every tech stack without effort.
- It's super easy to create new content types and retain relationships previously created.
- The visual editor is what our customers love and what helps developers understand business needs
- The whole product has a DevOps mindset which is very important in Enterprise: Workflows, backups, APIs. It's an invaluable tool inside every business process we have running
- The image service is on par with dedicated image SaaS tools and fully integrated into the solution. More value for my money
- It's super easy to create new content types and retain relationships previously created.
- The visual editor is what our customers love and what helps developers understand business needs
- The whole product has a DevOps mindset which is very important in Enterprise: Workflows, backups, APIs. It's an invaluable tool inside every business process we have running
- The image service is on par with dedicated image SaaS tools and fully integrated into the solution. More value for my money
What do you dislike about the product?
I can hardly find anything to dislike. Every experience from setup to support has been nothing but positive.
What problems is the product solving and how is that benefiting you?
Maintaining customer sites of all sizes from small landing pages to multi-page documentations (2500+ pages). The immediate benefit I got was a true separation of concerns: People start managing content again, creating heaps of knowledge without being forced to think about representation. But due to the excellent visual editor, you literally never lose sight of the final result. This is UX at its finest Focus on the core task, make aware of the entire picture.
Due to the unique separation of content into separate units called Bloks, content teams are faster than never before. The content becomes a manageable mesh, rather than a deeply nested tree of pages. Content creators can navigate a lot easier.
Due to the unique separation of content into separate units called Bloks, content teams are faster than never before. The content becomes a manageable mesh, rather than a deeply nested tree of pages. Content creators can navigate a lot easier.
Storyblok helped us to reduce the complexity of content management
What do you like best about the product?
We have a lot of product data and user-generated content which we wanted to make available on our website. With traditional content management systems, it was very difficult to integrate those things. Storyblok gave us the flexibility we needed. Furthermore, we love the speed and performance of the Storyblok admin interface. This enables our content editors to do their job faster and spend less time waiting for things to load. Also, the visual editor works great and makes it possible for non-technical people to write and edit content as well.
What do you dislike about the product?
We are very satisfied and do not have any issues
What problems is the product solving and how is that benefiting you?
We had several challenges which our old CMS:
1.) integrate our data which is produced for our apps and other products into our website
2.) improve the performance and loading speed of our website to improve SEO metrics
3.) make content editing faster and more fun for our content editors
Regarding 1: since Storyblok provides all the data as JSON and our product-data and user-generated content is served by a REST API it was easy to combine those two APIs. We were able to use programming languages and frameworks we love and know and weren't locked into the technology which was used and defined by the old legacy CMS.
Regarding 2: To make it easy for our content editors to work with the old CMS we installed lots of plugins and over time the website became pretty slow. Also after applying all caching and performance tips and tricks we weren't fully satisfied. Because of the great structure of the Storyblok API it was possible for us to implement very aggressive caching and basically save the final HTML on the webservers disk. This brought is nearly "static site" performance but with the possibilities to edit content within the Storyblok admin interface.
Regarding 3: Another problem which was very annoying for our content editors, was the problem that the admin interface of the old CMS loaded very slowly. Therefore they spent most of the time waiting for the admin interface to load. Even correcting a typo took them minutes because they needed to navigate through the site structure and needed to wait on each click. The Storyblok admin interface is very fast and snappy and you can click through it without spending time looking at the loading spinner. Also, the visual editor and live updates are a great improvement for our content editors. Now they can edit content very fast and are not slowed down by the CMS tool.
1.) integrate our data which is produced for our apps and other products into our website
2.) improve the performance and loading speed of our website to improve SEO metrics
3.) make content editing faster and more fun for our content editors
Regarding 1: since Storyblok provides all the data as JSON and our product-data and user-generated content is served by a REST API it was easy to combine those two APIs. We were able to use programming languages and frameworks we love and know and weren't locked into the technology which was used and defined by the old legacy CMS.
Regarding 2: To make it easy for our content editors to work with the old CMS we installed lots of plugins and over time the website became pretty slow. Also after applying all caching and performance tips and tricks we weren't fully satisfied. Because of the great structure of the Storyblok API it was possible for us to implement very aggressive caching and basically save the final HTML on the webservers disk. This brought is nearly "static site" performance but with the possibilities to edit content within the Storyblok admin interface.
Regarding 3: Another problem which was very annoying for our content editors, was the problem that the admin interface of the old CMS loaded very slowly. Therefore they spent most of the time waiting for the admin interface to load. Even correcting a typo took them minutes because they needed to navigate through the site structure and needed to wait on each click. The Storyblok admin interface is very fast and snappy and you can click through it without spending time looking at the loading spinner. Also, the visual editor and live updates are a great improvement for our content editors. Now they can edit content very fast and are not slowed down by the CMS tool.
Recommendations to others considering the product:
I think it's important to understand the concept of a headless-CMS and how it is different from a traditional CMS. Of course, there are open-source CMS which are free but Storyblok offers a lot for the price, and for us, the break-even was from day one. It enabled us to focus on creating an awesome website and writing great content and didn't have to think about all the infrastructure topics which come along when you have to manage your own open-source solution.
Storyblok, the headless CMS of our enterprise JAMstack solution
What do you like best about the product?
It is incredibly good to work with:
Editors love the visual editor and the freedom to change content within seconds, developers love the component structure and the helpful team behind Storyblok.
Editors love the visual editor and the freedom to change content within seconds, developers love the component structure and the helpful team behind Storyblok.
What do you dislike about the product?
We would love to see a customizable naming of the components for the editors.
What problems is the product solving and how is that benefiting you?
We are developing enterprise-scale websites with Storyblok and Netlify. Now our clients have got a future-proof web development architecture. The benefits are top performance, scalability and ease of use for the businesses. Our clients do save $ in comparison with CMS solutions like AEM without compromises on their product website.
The missing piece in the Headless CMS scene
What do you like best about the product?
We absolutely love the editor experience, it is a breeze to get used to and learn to use, the plugins system makes it extremely powerful and we are very happy to use it on a daily basis for a dozen of sites!
What do you dislike about the product?
The only missing piece we currently have is to have an additional "databases" or "collections" concept which could allow us to store and manage structured data in a headless way with the same awesome editor Storyblok offers, currently we have to store this data in another CMS and have the consuming application load data from two sources.
The difference to what is currently offered could be that instead of treating everything as "pages" and "components" you could also add arbitrary collections of "person", "product", "venue" etc and then use those just like you do datasources. (perhaps making datasources a bit more powerful?)
The difference to what is currently offered could be that instead of treating everything as "pages" and "components" you could also add arbitrary collections of "person", "product", "venue" etc and then use those just like you do datasources. (perhaps making datasources a bit more powerful?)
What problems is the product solving and how is that benefiting you?
Storyblok brings an unprecedented level of flexibility and control to the Headless CMS scene. Before we started using it, using a Headless CMS seemed like a great alternative for simple sites or sites with a clear structure.
Storyblok allowed us to unleash the creativity of our editors and site managers by letting them see the content changes in place, a familiar experience to many webmasters.
The Headless nature of Storyblok made it easier for us to repackage the content for different distribution channels with ease, which was mind blowing! :)
Storyblok allowed us to unleash the creativity of our editors and site managers by letting them see the content changes in place, a familiar experience to many webmasters.
The Headless nature of Storyblok made it easier for us to repackage the content for different distribution channels with ease, which was mind blowing! :)
Recommendations to others considering the product:
Don't think too much about it, give it a try and you'll absolutely love it!
Marvelous and enjoyable development and editing experience with this peerless headless CMS!
What do you like best about the product?
The implementation and workflow of setting up projects from a small portfolio page to an enterprise-level product in any significant framework you prefer are excellent.
Developers, Editors, Employees, and Customers enjoy working with the headless CMS through the Visual Editor and other critical aspects of Storyblok. The visual Editor is a crucial aspect for Editors and Developers alike to enjoy working with this headless CMS.
Storyblok even supplies an image CDN Service with query syntax that is highly beneficial in most projects.
Extending any out-of-the-box functionality with plugins, apps, or field types is easy and enjoyable for developers.
Developers, Editors, Employees, and Customers enjoy working with the headless CMS through the Visual Editor and other critical aspects of Storyblok. The visual Editor is a crucial aspect for Editors and Developers alike to enjoy working with this headless CMS.
Storyblok even supplies an image CDN Service with query syntax that is highly beneficial in most projects.
Extending any out-of-the-box functionality with plugins, apps, or field types is easy and enjoyable for developers.
What do you dislike about the product?
Some base functionality and workflow bugs are still there and take longer to get fixed or be on the roadmap to get extended.
But the active Github Issue Backlog, consistent fixes and extensions throughout the Storyblok team, and a growing community easily make up for it, though!
But the active Github Issue Backlog, consistent fixes and extensions throughout the Storyblok team, and a growing community easily make up for it, though!
What problems is the product solving and how is that benefiting you?
We use Storyblok mainly at our best-of-breed solutions agency, Vertex Media Technologies, which crafts best-practice products based on the best tools and tech for the situation.
Storyblok is an everyday tech. We base around 90% of our solutions on other bleeding-edge technologies like Nuxt, Vue, Cloudflare, etc.
It has become the one-size-fits-all solution for all our content and data needs.
We developed extensive expertise and found all the best practices in using it over the last five years. We can recommend it with good conscience to anyone interested in having the best balance of Content Editing and Developer Experience in a content management system you will probably ever find there.
We grow projects with this best-of-breed headless CMS quickly, from a one-pager portfolio to a product managing more than a few thousand stories or pages without worrying about anything as long as we keep what we are doing in mind. Working content and configurations for large-scale enterprise-level products like real estate platforms, e-commerce shops, or inventory management systems was no problem creating and maintaining comfortably.
Every product benefits from the extensive functionality and community around this peerless headless Content Management System.
Storyblok is an everyday tech. We base around 90% of our solutions on other bleeding-edge technologies like Nuxt, Vue, Cloudflare, etc.
It has become the one-size-fits-all solution for all our content and data needs.
We developed extensive expertise and found all the best practices in using it over the last five years. We can recommend it with good conscience to anyone interested in having the best balance of Content Editing and Developer Experience in a content management system you will probably ever find there.
We grow projects with this best-of-breed headless CMS quickly, from a one-pager portfolio to a product managing more than a few thousand stories or pages without worrying about anything as long as we keep what we are doing in mind. Working content and configurations for large-scale enterprise-level products like real estate platforms, e-commerce shops, or inventory management systems was no problem creating and maintaining comfortably.
Every product benefits from the extensive functionality and community around this peerless headless Content Management System.
Recommendations to others considering the product:
It is probably the best headless CMS around, easily extendable if you miss something in the growing out of the box features and functionality, and the support, employeens and partnership is a charm.
The best headless content management platform around.
What do you like best about the product?
Ease to use and performance is great. Especially that there is a visual editor makes integrated and using the platform easy for non-technical users. Feature set is very complete and the API first approach allows easy customisation and adding of functionality. It's also great to have a growing network of partners, that can help with integration - so that it is possible to really focus on UI/UX and be assured that backend/performance/process are just doing what they should do.
What do you dislike about the product?
They are not as well known as wordpress or other older systems, so there are still less people familiar with their system.
What problems is the product solving and how is that benefiting you?
Very performant and clean site, complete separation frontend / backend, flexibility to change UI/UX but have a scalable system in the backend, product that non-technical editors and writers can work with.
Recommendations to others considering the product:
If you choose a headless CMS or content platform I would strongly look into ease to use for editors and performance. We have seen storyblok by far outperforming competing systems in these regards.
Storyblok is a breakthrough Headless CMS with its unique visual editor and block-based structure.
What do you like best about the product?
Storyblok's key feature it the block-based structure which allows the content editors to reuse components when building their webpages. They also nail the Internationalisation of the content in the CMS.
What do you dislike about the product?
They have a lot of awesome features which they don't flesh out properly in their documentation.
What problems is the product solving and how is that benefiting you?
We are capable of building websites in record time. Their structure also enables our company to build our own tools on top.
Recommendations to others considering the product:
Read their documentation and setup guides for setting up your first project in Stroyblok.
The best CMS I’ve used - the sweet spot between power, flexibility and ease of use
What do you like best about the product?
It’s the full package that works so well for me, Storyblok feels like a well thought out and complete product.
As a developer I love how it easily allows me to build complex structured and related data but for a content editor they can use a visual editor and see their changes quickly and easily.
The API is easy to work with and outputs JSON so can be consumed and transformed as needed using whatever technology stack you’re comfortable with - Vue, React, Laravel etc.
Headless CMS’s clearly are the future, decoupling the content from the frontend makes so much sense. So often a website suffers because the frontend is so tightly coupled to the content management system that upgrading it means upgrading everything. With a headless CMS you can freely replace the frontend whilst retaining the existing backend or push the same content to multiple channels.
The team is fantastic too, iterating and improving the product with new features and always friendly when offering support.
As a developer I love how it easily allows me to build complex structured and related data but for a content editor they can use a visual editor and see their changes quickly and easily.
The API is easy to work with and outputs JSON so can be consumed and transformed as needed using whatever technology stack you’re comfortable with - Vue, React, Laravel etc.
Headless CMS’s clearly are the future, decoupling the content from the frontend makes so much sense. So often a website suffers because the frontend is so tightly coupled to the content management system that upgrading it means upgrading everything. With a headless CMS you can freely replace the frontend whilst retaining the existing backend or push the same content to multiple channels.
The team is fantastic too, iterating and improving the product with new features and always friendly when offering support.
What do you dislike about the product?
I can’t think of any major issues. There was a bit of a learning curve about how to best consume the API and structure content but nothing more complicated that any other CMS.
What problems is the product solving and how is that benefiting you?
I’ve used and made a lot of content management systems over the years and they’re all suffered from similar problems. They either lack the flexibility to create the desired content structure, are very cumbersome to use, become ‘plugin hell’ with a mishmash of varied GUIs and duplicated functionality or are very hard to update.
Storyblok solves all other these issues. You build any schema you want for your data using a range of fields such as images, richtext, relationship links, or create your own VueJS based plugins. The interface is very clean and simple to use for editors - much of it takes place in the visual editor that allows content editors to see changes swiftly. As it outputs JSON you are free to totally change the website when updating without the usual migration headaches.
Storyblok solves all other these issues. You build any schema you want for your data using a range of fields such as images, richtext, relationship links, or create your own VueJS based plugins. The interface is very clean and simple to use for editors - much of it takes place in the visual editor that allows content editors to see changes swiftly. As it outputs JSON you are free to totally change the website when updating without the usual migration headaches.
Storyblok is a solid Headless CMS which sets no limits in terms of project scope.
What do you like best about the product?
Content-Creation and schema modelling is a breeze to work with. The visual editor works rock-solid and gives content creator an easy to use tool to manage content. Beside that as a developer the API is separated into a management and delivery API what was the key feature why I started working with Storyblok. So everything can be either handled on the backend of Storyblok or via self-written APIs and services to provide the necessary data.
What do you dislike about the product?
Typings are currently limited, I would love that the GraphQL API would receive an update that I would start using it.
What problems is the product solving and how is that benefiting you?
Using it as a content storage and Headless CMS to replace TYPO3, Drupal and WordPress with a one drop-in solution
Recommendations to others considering the product:
It all comes down to the project but I found it very good to replace traditional CMS with Storyblok, increased speed of development especially if you manage multiple projects in one account.
showing 521 - 530