Unclaimed: Are are working at Storyblok ?
Storyblok Reviews: 4.5/5 — Highly Rated
Storyblok is the world's pioneer headless CMS that works for both developers & business users. Built on the premise that traditional CMS makes it difficult to repurpose content for different platforms, Storyblok offers a unique fusion of visual editing tools and highly tailored content blocks built on top of its headless architecture that provides exceptional flexibility and speed for developers.
| Capabilities |
API
CLI
|
|---|---|
| Segment |
Small Business
Mid Market
Enterprise
|
| Deployment | Cloud / SaaS / Web-Based |
| Support | 24/7 (Live rep), Chat, Email/Help Desk, FAQs/Forum, Knowledge Base, Phone Support |
| Training | Documentation |
| Languages | English |
Compare Storyblok with other popular tools in the same category.
The editor's user experience with Storyblok is flawless. Integration was easy for our developers to achieve.
Nothing in particular, some minor features are missing, like rich links (allowing for javascript attributes).
Help create SEO-relevant content that can be integrated into our eCommerce store. The headless, API-based approach makes for reusable content and easy integration.
it has a large FAQ section and the high customizability is a big pro
none so far that I have explored in my interactions
Using it for Nuxtjs frontend in my work and personal projects.
It's a no-nonsense headless cms with a great delivery API. Also it supports the types of nested content that supports structured content very well (like for producing website structure and slugs deep slugs).
The tooling is extensive with SDKs for several frontend frameworks. But, at the time of writing some of them could require better documentation and structure.
Using Storyblok as CMS for several websites and one content-based app.
It was very easy to implement Storyblok in our Nuxt application. And also very easy to create content with the visual editor. Everyone is satisfied with the new CMS
If i have to mention one thing, it would be that it isn't possible at the moment to filter published/unpublished stories. Which makes it hard to check where we have unpublished content.
Before Storyblok we had our content in the code, so we needed software developers to update the content of the page. With storyblok it is much easier. The development team can concentrate on the big things.
Storyblok makes it easier than ever to manage website content. All of my clients have mentioned how easy it is for them to go in and manage their website content. From a developer standpoint, Storyblok is excellent. They make it extremely simple to create new content blocks that can easily be implemented.
I don't really have anything negative to say about Storyblok. The only thing I would ask from the Storyblok team is to add built-in Typescript type definition generation. In the meantime, I created a npm package that does just that: https://www.npmjs.com/package/@brbndigital/storyblok
Being able to set up a CMS in a matter of minutes and have it integrated with whatever project I'm working on quickly is a massive time saver. Not only does it save me time in my development cycle, but it provides an easy-to-use interface to my clients so they can manage their own content without too much hand holding.
The implementation is easy and useful. The flexibility is also really good and the support helped us out multiple times.
Better comparison tools between different spaces so you can easily upgrade them.
We developed our own PWA Odoo application and this is a great asset to the stack. Multiple webshops are being made more flexible thanks to this feature.
The visual editor combines the atomic component approach with the ability to directly see the result of your work. That way it's easy to make sure your content behaves like intended.
Sometimes it's hard to wrap your head around the fact that storyblok is *only* a content hosting platform, if you come from an old CMS that are mostly all in one solutions for content, forms, business logic and whatever else you need.
While developing very specialized tools for customers, they often want some kind of content function. Instead of re-inventing the wheel, we can just outsource that part to storyblok and concentrate on the business logic.
It's very easy for anyone regardless of tech background to make updates and changes to the site.
I don't have dislikes of Storyblok based on my role in using it.
The marketing team owns the website and has varying degrees of CMS knowledge. Storyblok makes it much easier to divide the work among many since it's so user-friendly and straightforward for any skillset.
The visual editing experience is great. My coworkers in marketing who have been using it for the past 6 months have had only good things to say about it. Its so easy for developers to extend and for marketers to use.
The permissions are very granular but could be even more so! I'd like to have more control over exclusions of different content types.
Allowing marketers to create content without developers, and quickly see their work before it goes live. It has improved our publishing experience for everyone.
Storyblok provides a complete solution when it comes to a content management system and much more. It comes in with a visual editor which enables content creators to create and update their website's look feel as well without any help from developers. As its core offering, Storyblok provides a robust infra and an array of functionalities ranging from managing content (both website pages and blogs), tags, asset management, and even component creation. Using components, one can create reusable website widgets and use them on the fly as and when needed. Management of components is also fairly easy as is the whole user experience of the product. For the developer side, they provide APIs so that, if needed, Storyblok can also be used as only a CMS while one can have their front-end design. Overall it is a very usable and impressive product.
Nothing major. The app directory is still to grow I think but that will happen with time as adoption increases for the product as newer use cases would be identified with an ever-increasing user base.
We were exploring CMSs that provide APIs and also supports reusable components so that we can use our own user interface while do not invest in developing a CMS in-house.