Senior Software Engineer at a tech services company with 11-50 employees
Real User
Top 20
Jun 22, 2026
My main use case for Storyblok is using it for the CMS in various projects such as site migrations. We also do projects on a retainer basis, meaning we handle some of the projects that the client worked on with the previous agency, and then we took over. We continue working with those projects, so there are cases where we do the project entirely new as a site migration from other CMS to Storyblok, as well as doing the retainer project. A standout project where we used Storyblok would be the Royalton. For that project, we used Storyblok as a CMS and did the site migration from the old website to using Storyblok as a CMS for the new website.
Technical Architect at a tech vendor with 10,001+ employees
MSP
Top 10
Jun 21, 2026
Storyblok is primarily used for website development for many of our clients, as we use it as a headless CMS. One specific project where we used Storyblok as a headless CMS is a CSR initiative where we transformed the client's CMS from Squarespace to a headless CMS and improved the performance by many folds.
Full Stack Developer at a consultancy with 11-50 employees
Real User
Top 10
Jun 20, 2026
My main use case for Storyblok is mostly blogs and landing pages. I have used it in Astro and Next.js projects, in tandem with Vercel for deployment. The previous solution I used before Storyblok was Strapi, but it required payment if I wanted to use it in the cloud; otherwise, I would have to deploy it myself. Before choosing Storyblok, I evaluated Contentful, but I simply could not use it. There was a strange error when I tried to access it.
The main use case for Storyblok is developing websites with content management system ideas, so we manage all the content by using a React structure, mapping the blocks inside Storyblok. There were also some import features. We created scripts to import content from other CMS into Storyblok. One project that illustrates my use of Storyblok is the Louisiana portal, which is a government portal. They decided to use this real-time editor, CMS, and real-time viewer. The idea was to build all the design in a React Next.js project and then map the components into Storyblok. They would be able to build their content based on the structure of the old website, but in the new design and new CMS. The idea was to import everything into Storyblok and let them make the edits and create new pages. We had two or three main templates, and then they were free to create different page variations there according to their necessity. They had a lot of content, which was really challenging because of the different menus and structures, resulting in different templates as I mentioned before. It was really great to work on that project.
My main use case for Storyblok is that we use it as the content management system for our client websites, so we're an agency and nearly every website we build will use Storyblok as the system that we choose. A specific example of a client project where we used Storyblok is one we did recently for a charity association where we live, and we integrated Storyblok into Laravel as the platform for running the website. Storyblok enabled us to build the templates and all the blocks that they required for the pages on the website to create all the content. What was useful about it, because it's platform agnostic, is we could also then use a Filament back-end as well on Laravel, allowing charities to have an individual back-end just for their content, but the richer branded pages we built fully in Storyblok so that our client could manage everything very easily and quickly, such as building new pages based off the block library we created for them, and enabling things including automatic image optimization, allowing them to choose icons, color them from their palettes using custom Storyblok plugins, and other features. Storyblok gives us the flexibility to rapidly respond to client needs because every client project is going to be different, and it allows us to manage that in a simple interface which we love and our clients love too.
My main use case for Storyblok is that it is a headless content management system for me. I set up content in Storyblok, and then I use the Storyblok API client to manage it. Storyblok is not deployed anywhere; I access it through the API, and it is publicly available. While I have my keys, it is software as a service, so it is a headless CMS, and I do not have to deploy anything; it is just accessible for me through the internet.
Storyblok is a flexible headless CMS designed to manage content efficiently through a hierarchical structure, allowing developers and marketers to work collaboratively without disruptions. Storyblok empowers businesses by facilitating easy content management and consistent digital experiences across channels. It holds a unique position by combining visual editing with advanced content workflow capabilities. Developers appreciate its API-driven approach that separates content from its...
My main use case for Storyblok is using it for the CMS in various projects such as site migrations. We also do projects on a retainer basis, meaning we handle some of the projects that the client worked on with the previous agency, and then we took over. We continue working with those projects, so there are cases where we do the project entirely new as a site migration from other CMS to Storyblok, as well as doing the retainer project. A standout project where we used Storyblok would be the Royalton. For that project, we used Storyblok as a CMS and did the site migration from the old website to using Storyblok as a CMS for the new website.
Storyblok is primarily used for website development for many of our clients, as we use it as a headless CMS. One specific project where we used Storyblok as a headless CMS is a CSR initiative where we transformed the client's CMS from Squarespace to a headless CMS and improved the performance by many folds.
My main use case for Storyblok is mostly blogs and landing pages. I have used it in Astro and Next.js projects, in tandem with Vercel for deployment. The previous solution I used before Storyblok was Strapi, but it required payment if I wanted to use it in the cloud; otherwise, I would have to deploy it myself. Before choosing Storyblok, I evaluated Contentful, but I simply could not use it. There was a strange error when I tried to access it.
The main use case for Storyblok is developing websites with content management system ideas, so we manage all the content by using a React structure, mapping the blocks inside Storyblok. There were also some import features. We created scripts to import content from other CMS into Storyblok. One project that illustrates my use of Storyblok is the Louisiana portal, which is a government portal. They decided to use this real-time editor, CMS, and real-time viewer. The idea was to build all the design in a React Next.js project and then map the components into Storyblok. They would be able to build their content based on the structure of the old website, but in the new design and new CMS. The idea was to import everything into Storyblok and let them make the edits and create new pages. We had two or three main templates, and then they were free to create different page variations there according to their necessity. They had a lot of content, which was really challenging because of the different menus and structures, resulting in different templates as I mentioned before. It was really great to work on that project.
My main use case for Storyblok is that we use it as the content management system for our client websites, so we're an agency and nearly every website we build will use Storyblok as the system that we choose. A specific example of a client project where we used Storyblok is one we did recently for a charity association where we live, and we integrated Storyblok into Laravel as the platform for running the website. Storyblok enabled us to build the templates and all the blocks that they required for the pages on the website to create all the content. What was useful about it, because it's platform agnostic, is we could also then use a Filament back-end as well on Laravel, allowing charities to have an individual back-end just for their content, but the richer branded pages we built fully in Storyblok so that our client could manage everything very easily and quickly, such as building new pages based off the block library we created for them, and enabling things including automatic image optimization, allowing them to choose icons, color them from their palettes using custom Storyblok plugins, and other features. Storyblok gives us the flexibility to rapidly respond to client needs because every client project is going to be different, and it allows us to manage that in a simple interface which we love and our clients love too.
My main use case for Storyblok is that it is a headless content management system for me. I set up content in Storyblok, and then I use the Storyblok API client to manage it. Storyblok is not deployed anywhere; I access it through the API, and it is publicly available. While I have my keys, it is software as a service, so it is a headless CMS, and I do not have to deploy anything; it is just accessible for me through the internet.