Storyblok

My main use case for Storyblok  involves clients that need custom websites and custom products. I have been using Storyblok  for Shopify  and Hydrogen, primarily for clients needing customization and complete control over their websites.

A specific example of a project where I used Storyblok for a custom website is with a perfume brand, where we had the products in Shopify  Hydrogen, but we needed custom slugs and custom product contents. We used Storyblok for the optimization and connected both of them together.

Storyblok has positively impacted my organization because I have used other CMS options before, but with Storyblok, the live preview and overall setup have changed the client's feedback and the level of customization.

The live preview and setup have improved client feedback significantly. I used to get comments from clients saying that they were worried when adding text that it would destroy their content. Now, with the live preview of Storyblok, the client knows exactly how the content they are going to put will impact their website, and they can preview it on all mobile devices, giving them freedom they never thought they would have.

The best features Storyblok offers include customization, data components, data sources, and deep customization options, with many layers for publisher, administrator, and scopes on the content.

One of the most valuable features for the current projects I'm working on is the customization of all the custom blocks, as it gives a truly custom touch to the clients. Most of the clients need to have full control over their websites, and this provides them with the biggest freedom, along with the live preview.

It is difficult for me to give a comprehensive answer regarding how Storyblok can be improved, as nothing is perfect and this would require considerable time to think about thoroughly.

I chose eight for my rating because I believe Storyblok still needs to work on localization, slugs, auto-translate, and all the plugins related to this part.

Regarding Storyblok's AI capabilities, I think they could do much better because the translation is not fully automated yet, and the slugs and SEO parts represent huge opportunities for improvement.

I have been using Storyblok for almost four years.

Storyblok is stable.

Storyblok is really scalable, but it's important to be careful with the requests, as the pricing and requests can go up really high.

The customer support is really great, depending on whether you have a contact there.

I have previously used different solutions such as Dato and Sanity , along with plenty of other CMS options. However, Storyblok with the live preview and the entire environment it provides has changed the whole setup.

My experience with pricing, setup cost, and licensing varies depending on the client's needs, but I have used many licenses, including the free option, the first tier, and the last premium part.

My company has a business relationship with this vendor, as we are partners.

Since Storyblok is mostly for the clients and not for the employees, it's difficult for me to give a comprehensive answer about the return on investment in terms of fewer employees needed, money saved, or time saved.

My experience with pricing, setup cost, and licensing varies depending on the client's needs, but I have used many licenses, including the free option, the first tier, and the last premium part.

Before choosing Storyblok, I did not evaluate other options.

My advice for others looking into using Storyblok is to dive fully into it and immerse yourself in Storyblok's environment. I gave this review a rating of eight.

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.

We are mainly working with headless CMS, and Storyblok is one of the criteria. It has its own advantages over other CMS in the industry, such as a great interface and various options for doing many things. That is the reason we choose Storyblok, depending on the use case of the project.

One of the best features Storyblok offers is the ability to do modeling, where we can reuse component modeling or block modeling inside any page structure or component structure. This feature is really helpful and has aided us in the development part. It is a feature I value highly.

Component modeling has indeed saved my development time when I think of the component as an individual block, whether it is a small block, a medium block, or a bigger block. Once I do the modeling for a smaller block, I can reuse that anywhere inside Storyblok modeling, making it very useful. In some other CMS, there are restrictions on where the component modeling can be used, but Storyblok allows the developer to make use of that modeling, so I do not have to model certain components every time. I can reuse and make my development faster.

For content editors, one of the standout features would probably be the editing process, as users can switch between form view or visual view to see the live content they are currently editing. I also value the copy and cut feature, where you can copy a component or cut a component, switch the tab and still paste the content. That is a really great feature.

Storyblok has positively impacted our organization by helping us do projects in a certain way with its really great features. Storyblok also offers excellent documentation, project setup, and support. Additionally, it is a popular headless CMS with great features and many integrations supported, which I think is fantastic.

In terms of the migration process during development, the content modeling process has worked really well for us. Storyblok contains an SEO field out of the box so that editors can make use of that field to improve their SEO. There is also AI SEO integration, as well as other great tools depending on the project use case, such as the multi-language and AI translation integrations that help both us and the clients.

I believe there are some parts that definitely can be improved inside Storyblok, such as the way content is listed out in certain areas, which makes it a little difficult to delete content.

I would add another point about the content import and export feature. If Storyblok could implement that inside the platform, that would be great. I encountered a few projects where clients needed that feature, as other CMS have that capability. Having import and export options would help editors enter a lot of content rather than editing it one by one. While there is an API that can be used, there is no interface for easy content import and export by the editor within Storyblok.

Regarding areas where Storyblok could use further improvement, I suggest implementing the import and export feature. Also, the content editing experience could be enhanced; for example, in pages with a long list of components, it becomes challenging to navigate when items start to accumulate. For instance, if we implement many redirects, the load more option becomes cumbersome. A list view for editing experiences would be helpful, and implementing multiple selection or select all features could significantly enhance usability.

I have been using Storyblok for two and a half years.

Storyblok is stable. I have yet to experience any downtime while accessing Storyblok CMS during my two and a half years of use.

Storyblok has potential for scalability, as it can be done on demand. You can increase your project selections based on your organization's licensing needs. For instance, if you are starting with a small site and it grows, Storyblok can scale accordingly without issues.

Before choosing Storyblok, we certainly evaluated other options. The CMS that our company often considers include Storyblok, Contentful , and Agility CMS, so those are the top three CMS we have been working with.

I usually access Storyblok through the browser, and typically the team or client sets up the Storyblok account for access.

I am not entirely sure about the return on investment metrics. I can say that certain functionalities provided by Storyblok are superior to those offered by other CMS. As I mentioned, Storyblok's content modeling and features such as translation and other necessary integrations are why it is often chosen over other CMS. Pricing may also factor in, but I am more focused on development than on pricing metrics.

My advice for anyone looking into using Storyblok is that if you are searching for a headless CMS with great potential and tools, Storyblok should definitely be one of your options. The documentation is fantastic, and there are many integrations available for various technological platforms, whether that is Next.js or other front-end frameworks. Even those from various front-end backgrounds will find it easy to integrate content within Storyblok, allowing for numerous modeling and setup options for your pages. I would rate this product an eight out of ten.