Storyblok Reviews & Product Details

Able to create new page to customize site centric to user.

Switching between preview themes can be tricky.

Customer can handle content and create page without our need of developpement.

Super easy to add in to any existing next.js project. Great support when something goes wrong. Lots of features being added in the years we have been using it.

It has got a lot better over the years we have been using it; however it would be nice to have support for more generic sitewide options pages.

Mostly next.js applications needing a headless CMS

The implementation of Storyblok is based around ATOMIC design principles which allows a component first approach and makes it easy to implement. The custom fields plugin which is part of the application allows you to build content from other APIs into the content of your page or Blok and makes it the perfect itegrations addon. Along with the Live Preview for each environment, Test, UAT or Prod, makes this the best in class!

Some more case studies and code based case studies would be great!

The seperation of the CMS is important to allow frontend developers to keep your website fresh. Storyblok is fast and very scalable!

Most helpful part of Storyblok is the layout and the ease at which we can navigate the back end of the website to make changes shown on the front end

Sometimes can be tricky importing and uploading assets to the asseet library and then adding them onto a specific page

We had issues with website layout and updates that this has now fixed for us

Versatile system. Rich with applications and functionalities. Easy to build and to update.

Nothing so far. With as much as I try, all is good.

Easy to manage.

With Storyblok, it's incredibly easy to amend content on the site, everything is organised and with a well-set up site, almost no team training is required. It's also incredibly easy to integrate all of your core applications.

I've not come across any downsides to Storyblok. I guess I wish we could integrate Bynder without having to upgrade.

Storyblok allows us to quickly and easily create content for our website and allows us as an internal marketing team to manage the whole site without having to rely on developers.

The reusability and the design system that Storyblok boasts integrates itself seamlessly into our way of working and our codebase. We've created more than one site using the same library of components and now simply seek improvements to the way that we're working with these components - and the spaces that utilise them. We use Storyblok every day as part of our work, whether it's developing a new feature or just creating a funky new page to show off the art of the possible. It's been so easy to create new content on the site that we find ourselves - even as developers - making fake content pages just to show off the work we've done and what can be acheived with it.

V2 fixed a lot of the quirks and problems that we'd previously noted. It's a much slicker experience. My least favourite part of Storyblok, however, is how the Releases app seems to be a bolt-on to the content creation process. There are still inherent bugs and quirks with getting it to slot nicely into our spaces. For our teams, it feels absolutely vital, so it'd be nice to see it get more of a focus.

It encourages the creation of reusable components that can be inserted within each other. This aligns with our development principles and ensures that we are not making everything bespoke, saving us time and also allowing the content teams to experiment more with what's available to us. That in turn leaves us with less pressure to guide them design principles.

From a developer perspective I really enjoy working with the technologies used. Libraries are available open-source and are always updated for use with various technologies. Support is quick, helpful and very engaged.

On major upgrades or launches of new libraries, documentation and source code sometimes don´t match, but that´s just a minor issue.

Providing an CMS with up-to-date APIs and technologies, supporting all our needs.

I recently had the opportunity to work with Storyblok for an ecommerce product MVP, and I must say that my experience with this platform has been nothing short of fantastic. Developer-friendly GraphQL API: The schema is well-documented and easy to understand, making it a breeze to query and manipulate data. I could retrieve exactly the data I needed without any over-fetching, which is crucial for optimizing performance. Intuitive UI and UX: Content editors and developers will appreciate the simplicity of the interface, making it easy for non-technical team members to manage content with minimal training. The real-time preview feature significantly streamlines the content creation process. You can see exactly how your content will appear on the live site as you edit it, which is a game-changer for developers working closely with content creators. This results in fewer iterations and a faster development cycle. Content localization and versioning: Storyblok's built-in support for content localization is a lifesaver, especially for ecommerce projects targeting international markets. The ability to manage content in multiple languages within the same project simplifies the process of creating a global presence. Furthermore, Storyblok's versioning system ensures that you can track changes, rollback if necessary, and maintain content consistency across various stages of development.

The GraphQL API documentation is not always up-to-date and this can be improved.

Storyblok simplifies content management for developers and non-technical team members. It streamlines the process of creating, editing, and organizing content, reducing the back-and-forth between developers and content creators.

Storyblok excels due to its framework-agnostic approach, offering seamless integration with any preferred framework. Whenever I encountered challenges, the proactive Storyblok team was immediately available on Discord to guide me towards a solution. Even as a novice developer, I effortlessly incorporated it into a system tailored for both SvelteKit and Storyblok. I consistently choose Storyblok for my projects, and the positive feedback from clients reinforces this decision. Furthermore, Storyblok is rich in features, boasting an array of data types (bloks) and an expanding suite of integrations, particularly its exemplary image service, which has notably optimized the website sizes I work on. I highly recommend Storyblok for its adaptability, support, and robust feature set.

I wish storyblok had a more visual approach to sharing blok-schemas across projects. Currently they offer a CLI but the entire approach is relatively hands-on. It's similar to copy and pasting files in a way, and I think this could be achieved with an inbuilt app-like approach of drag and drop.

I aimed to develop a system reminiscent of platforms like Webflow, where options and components are visually driven yet steered by my unique code. Storyblok empowers me to design and replicate a template that seamlessly integrates into every client project. This grants clients the speed and efficiency akin to low-code builders. However, it also provides the flexibility to tailor any specific design or development need. With just the initial version of my system, I'm already thrilled with the outcomes. Achieving such results without Storyblok or spending months crafting a less satisfying experience would be inconceivable.