Storyblok Reviews: 4.5/5 — Highly Rated

- It's ridiculously easy to structure your content logically - Content types and hierarchies - easy to use for non techy types - super extensible - supports multiple content formats - will make your marketing team happy - developers enjoy it too - great built in security

As a developer I do wish certain features for power users were more readily available, or that we could perhaps set up more powerful content rules and have the tools in the app to enforce them.

Delivering top-quality content to various different channels in a unified manner. Using it as a headless CMS for my clients(Freelance web developer/designer)

The ease of getting started and ready to plug in to my project.

I didnt like all of the layout of the cms but that was more from an esthetic point of view.

I used it to learn about cms as a concept and foubd an excellet tutor in storyblok.

We really like how we can "build anything" with Storyblok and make it super simple to use for the marketing team.

Nothing major. Would be awesome if it had a native split testing function.

Our previous website built on Wordpress was coded to where our non-technical employees couldn't make changes beyond uploading content. Storyblok solved that.

Storyblok was directly intuitive. Very quickly the structure behind it could be understood.

Instructions were not exactly easy to understand at the beginning. You might want to choose a flatter start here.

Try another headless CMS. Flexibility was the decisive advantage here

- WYSIWYG preview, the preview is awesome. - Custom data strucutre. - Publish approval progress.

- Assets preview, can't the whole image in assets list (seems they have improve this in v2)

Easily to build a static webpage, it's easy for engineering and content to work together.

Self-hosting a CMS for a website can be painful when it comes to regular maintenance tasks - applying security patches, updating the database, and adapting your custom backend code to changed APIs. Using Storyblok as your 'content repository' you can avoid this hassle and focus on your frontend code without worrying about future backend upgrades.

Once your web project starts growing, you might soon reach a point where the feature set of the free 'Community' account doesn't cut it anymore. Going from 'free' to '90 Euros/month' ('Entry' plan) is not for the faint of heart.

Website Content Management. No setup, no maintenance, and a powerful editing interface out-of-the-box. Plus it's really easy to build your own content editing components based on Vue.js

Dedicated integration with Magento, responsive developers through github issues

Actually there is nothing to dislike - I like the general idea to have content served from external service.

I was only checking it for Magento, since Magento's default CMS features are quite limited, I wanted to see if there is a better way of doing ut.

The visual editor is a great help to our client. The generous quota on the number of content types is also liberating compared to competitors offering the same service.

The ecommerce integration requires a higher plan, which is the only feature that requires an upgrade from the entry to the team plan, and a big blocking decision for our smaller cllients. We prefer to have the ecomm integration available on all plans (not free) as a gesture of goodwill for users supporting your platform.

As a digital agency, our client's content editing experience is very important to our collaboration. This is because if they are confused or make a mess in the cms, it is more overhead for them and maintenance for our developers.

My favorite thing about SB are ease of content linking and schema definition.

SB doesn't provide relation fetching more than one level deep via their REST API.

Website CMS should be a solved problem by this point, and SB comes closesto that ideal from all the offerings I've tried so far. I've made one-too-many bespoke CMS in the past, and SB would have allowed me to skip that tedious part.

It was easy to start creating new pages based on our modules created by our developers. The preview option was really helpful in our page building process. As a team we were able to quickly create a content structure.

My biggest issue currently with Storyblok is that in their default UI it is panful to upload multiple items at the same time to the libraries. The solution for this problem is to change the UI to Storyblok v2, and with this new view, this issue is solved.

We need to quickly create and adapt our marketing landing pages. For B2B marketing we need to have a quick and efficient tool that enables us to go above and beyond in our daily job.

From a technical standpoint, enjoying full flexibility on the frontend layer while still getting an easy-to-achieve WYSIWYG experience is a deal-breaker. Storyblok is a catchy thing.

Adjusted pricing but as long as it goes hand-in-hand with the quality of the provided services, clients will remain happy. We are seeing a couple of improvements in the V2 beta already which is hopeful.

We as an agency are building Jamstack websites that are powered by a headless CMS by default. Fast frontends need fast CMS in the background and Storyblok is just that.

Storyblok's most attractive feature has to be its pricing structure. They make it incredibly inviting and easy to quickly spin up a new instance and begin building out a site. You never feel pressured into upgrading tiers when not necessary for your workflow, and there isn't a huge deal of feature segregation between tiers. Beyond its pricing, Storyblok is incredibly easy and intuitive to integrate with Jamstack setups such as NextJS, Gatsby and plain React. The visual editor is relatively easy to use, and no client that I've introduced it to has been unable to use it yet.

Some of the visual editor features can be a little unintuitive at times, and there're some features missing from the visual editor that would be high up on my list of priorities - such as the ability to set more customised/detailed default values for blocks.

The main benefit to Storyblok is the ease and speed of integrating it into an existing React setup. You can spin up a Storyblok instance and within a few short hours have a fully headless CMS powered site ready to go.

Even with limited knowledge of ReactJS, I was able to create quite a complex site using StoryBlok. The integrations were simple, the UX was clean and also found their customer support always quick and helpful

There were some missing features like being unable to comment on pages, however, that has since been updated on the new version. Would like to see some more integration with third-party tools like Figma etc.

I used StoryBlok for an internal site, that can be updated by multiple people. Pages and content are easily updated by people with little to no technical knowledge

component-based manage assets multiple users draft/published stages

no synced blocks no asset version control nested component structure sometimes can be time-consuming to update

company website non-developer coworkers can learn using it easily

The main thing would be the visual editor and also how easy it is to develop own blocks.

Sometimes when a page has many blocks it can become a little bit cluttered to navigate with the visual editor.

The main problem I am solving is offering great customixability and ability the client to manage their website by themselves.

User experience for editors is top-notch. When using Storyblok with NuxtJS the way how the content types or "bloks" sync with code is excellent. API is well documented. Smart Image Service!

I feel the pricing model still needs to be reconsidered. It used to be more moderate and now for some clients it's too expensive. Why limit some basic functionalities like translatable slugs and webhooks, especially if you are trying to compete with open source CMSs. The user experience is good, but some updates to content should be allowed to make from the preview window too (without using content management API).

Easy to use content management system for all sorts of applications.

All the features of a headless CMS with the power of a visual editor

The user interface and design sometimes feel cluttered.

Content management for developers with the easiness of a visual editor for marketers.

It's easy for non-technical users to use.

The design could be a bit more vivid, but that's a matter of taste!

Building landing pages is a breeze - the instant preview inside the CMS makes it fast to understand what the outcome will be.

Developer friendly, ease of use, community. The support it has to different languages/frameworks and how deep this support goes helping you to fine tune the details. The easy of use when creating components, the preview image that can be added to each component which makes a it easy for a publisher to select it from the pages. The JSON format used to consume their APIs.

Some basic functions are still lacking, despite being sitting in their github issues for a long time. These pain points should have probably be addressed before the launching of v2 UI. You can't invalidate the image cache properly, including the ones already added to pages. Some basic fixes are still needed and the backlog is growing bigger everyday.

Using it as a headless CMS for our Nuxt application. The flexibility for creating fields/components and the support integrating with Nuxt are the main benefits. Web content management is much easier with Storyblok.

Storyblok is very easy to navigate and access. It is a handy tool. It is easy to get videos and download them.

I don't dislike anything. It is an amazing program

I am able to search and research various content for work and home.

I appreciate Storyblok's strong capabilities in handling large-scale, multilingual projects, which is a significant advantage for content-heavy websites. We use it in all of our projects. Its features, such as the preview and drag-and-drop functionality, are impressive, providing a powerful toolkit for content editors. Storyblok is also commendable for its scalability, efficiently managing thousands of pages. Additionally, the customer support is noteworthy for being fast and friendly, enhancing the overall user experience with the platform.

Despite its strengths, Storyblok has areas that need improvement. The interface, while intuitive, can be overly complex, leading to confusion, especially for those who may not be as technically inclined. This complexity in Storyblok suggests a need for more streamlined navigation or better guidance. Furthermore, Storyblok's security features, particularly in roles and permissions management, are basic and could benefit from further development. The documentation is solid, but often out of date or hard to search. Also the speed at which Storyblok resolves feature requests and bugs, can sometimes be slower than desired.

Handling large complex and multilanguage websits and scale.

It's generally easy to use and I can create and publish a page from start to finish in minutes. I like that there are a couple of steps required before actually publishing a page which removes the worry of accidentally publishing something. There are several options for photo and text displays which I appreciate.

Since the last update, when you insert a link, it automatically opens that link in the same window. Previously, you had the option to select the same window or a new one.

We are able to reliably reach our audience thanks to Storyblok.

Easy to use for small scale projects, allows lots of customisations

unintuitive to use in big projects, because it has no real intuitive way of having some staging area

It is easy to use and allows us building webpages

Easy to use and fast to integrate to new user cases.

Missing more private mode options for some use cases.

Implement a multilingual version of our app and web interfaces, allowing non-coders to edit texts. We use storyblok to run and set up campaigns (planning to implement also surveys) for different versions of components for not coders.

The live editor is the best for me. It makes content editing easy

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

Easy editing content on landing pages, so clients don't depend on devs to do this

it create structured data, which can be use byt any app, to render dynamic content.

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.

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.

Content easy to find into folders, great search bar performances.

Not intuitive folder organization logic.

Being indipendent with the content updates. Being faster for creating unique content. I am more productive.

It's really easy to use, versatile and you can do a lot without writing a single line of code.

There are some small but annoying glitches, such as Storyblok suddenly logging me out in the middle of something important.

Storyblok makes my CMS work faster as it is intuitive, easy to use and bug-free.

The scalability and fast way to setup backend.

The thing I like least is the pricing. It's pretty expensive for small websites.

Maintaining a backend system.

Having multiple websites under roof, all of which can be quite different thanks to the headless CMS technology. Easy to manage multiple users.

Need of having individual licenses for each website makes it expensive. Would like a better plan for small companies that have multiple websites and users.

Having a headless CMS makes it easier to update the front end of our website without limitations. In our industry having a well designed website (both UX and UI) is very important, together with being able to integrate it with other transactioanl platforms in a seamless way.