Storyblok

My main use case for Storyblok is to manage content as a headless CMS for my Next.js projects. I create the content structure and components in Storyblok, and then I fetch the content through the API and display it on the website. The visual editor also allows the content team to update pages on their own, without waiting for the developer.

I have created one Saigo Hotel website in which I have used Storyblok as a headless CMS. For Saigo Hotel, I used Storyblok to manage the content of all the pages, including the home page, about page, and contact us page. All the details have been made dynamic with Storyblok. I built reusable components and fetched the content into the website with the API. The visual editor helps because all the contents and assets, such as images, videos, and URLs, come from Storyblok.

The main use case for Storyblok is that developers can create reusable content blocks, and the content team can update the content without asking developers every time. This makes content changes faster and keeps the content flexible.

In my organization, we have mainly worked with three or four projects, and Storyblok has made content management easier for our team. Developers do not need to handle every small content change, so the content team can make updates faster. It also helps us keep the content more flexible.

The primary benefit for us is saving development time on small content changes. The content team can update text, images, and page sections themselves, so developers can focus more on new features and other technical work.

For me, the best features of Storyblok are the visual editor, reusable content blocks, and the live API. The visual editor makes it easy to see changes, and the API gives me a lot of flexibility when building with React or Next.js.

I want to add information about the component-based structure. It helps us reuse the same block across different pages, so we do not have to build everything from scratch if it is component-based.

Storyblok does not need significant improvements, but some things, such as setup, could be a little easier for developers. There are some concepts and settings that take time to understand at first. A better beginner's guide and simpler documentation would make the learning process easier.

If the setup is component-based, it will be easier for us. The initial setup could also be more straightforward, especially when creating components and setting up the content structure. Clear examples for common React and Next.js use cases would also help developers get started faster.

Overall, Storyblok works very well for our cases. Better onboarding and more straightforward examples for new users would make it easier to get started.

I have been using Storyblok for almost three and a half years.

Storyblok is stable.

Storyblok scales well for growing websites and content. The headless setups make it flexible. I can add more pages, content, and components without changing the whole content structure.

The customer support is good overall. When I need help, the documentation is usually useful, and the support team is helpful when I have a specific question. I rate the customer support an eight out of ten.

Before, I used a CMS solution, but I moved to Storyblok because I wanted more flexibility for content and a better visual editing experience for the content team.

I can confirm that we have achieved time savings. The biggest benefit is that content teams can update the website themselves, so developers spend less time on small content changes. I do not have a specific financial number, but the improvement in workflow is noticeable.

I have experience with the pricing being reasonable for the features I needed. The setup was fairly straightforward, but understanding the different plans and features can take some time. I would recommend checking the price based on the project size and team needed.

Before choosing Storyblok, I focused on headless CMS options. I mainly compared them based on the editor experience, flexibility for developers, API support, and how easy it is for the content team to use. Other headless CMS options I have evaluated include Strapi and Contentstack.

I would rate Storyblok an eight out of ten. I choose eight because Storyblok offers flexibility, a visual editor, and reusable components. I deduct two points mainly because the initial setup can take some time to understand, especially for new developers.

Regarding Storyblok's AI capabilities, I believe security and control are important, especially when working with company content. I want clear control around data privacy, access, and how the AI uses the content. Overall, Storyblok should keep this area clear and transparent for users.

Storyblok's AI output is useful for basic content tasks, but I would still review it before using it in production. It can save time, but I do not think anyone should depend on the AI output without checking it.

Storyblok is deployed in my organization as a cloud-based SaaS platform, hosted in the public cloud. My content connects to Storyblok through its API to retrieve content. I do not have direct visibility into the underlying cloud provider Storyblok uses, but I only use Storyblok through its hosted SaaS platform and APIs.

I would recommend Storyblok if someone wants a flexible headless CMS with good visual editing. I would suggest trying it with a small project first and checking if the content structure and features fit the team's needs.