Storyblok Reviews & Product Details

Ability to build complex templates for my websites with shareable components. It is very easy to implement.

Nothing from the top of my head. I have to admit I needed a tutorial from that finish dev in order to fully understand how to use Storyblok

Managing content while keeping i18n in check.

The first thing that struck me about Storyblok was its clean and intuitive user interface. Navigating through the platform is a breeze, thanks to its well-thought-out design.

Currently, there are very limited 3rd party applications available but I would love if they will keep adding more.

Storyblok's architecture is designed for scalability, accommodating projects of varying sizes. Its modular content modeling approach enables users to adapt to changing project requirements without major overhauls.

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

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.

It's so simple to use, and we don't need to apply it 100% in our projects, we can customise it to fit the exact project needs. The visual editor is excellent, and something that several other headless solutions don't include, it makes it attractive for our clients who aren't super technical.

As it's designed to be completely component-based, we've had to build some specific components and Story types to handle things that perhaps would be OOTB in another CMS; for example redirections. But these workarounds are acceptable as the benefits we get from StoryBlok outweigh the occasional frustrations.

We want to offer beautiful static marketing sites to our clients, StoryBlok allows our engineers to write bespoke code, with components (Bloks) and the clients to have autonomy in their website without relying on us to make changes. Being headless, it allows us to build optimised sites without compromise.

The reason Storyblok is my favourite CMS is that it has both a great dev experience as well as content editing experience without making sacrifices when it comes to either. Their support is great as well!

Sometimes the tutorials for specific frameworks aren't perfect, but it's a minor issue. Other than that, no complaints here.

Allowing for a great content editing experience for non-technical people while still allowing us a lot of flexibility with how we set up and code the frontend. The visual editor is awesome!

Storyblok is very flexible in nature and this allows Storyblok to be perfect for lots of use cases. Content types and Nested Components allows complete control over the composition. Along with that Image Service, Management API and Apps are super helpful as well. For content editors, the Live preview helps a lot and they are able to make changes in no time.

The rate of feedback on Github issues and the feedback community could be increased.

Storyblok is helping us build compositions for any kind, be it Landing pages, website and in CMS as well. Storyblok image service is also amazing to scale assets as per the requirement.

It's a really flexible, powerful content platform that really allows you to shape your content and then consume it however you wish. It's really easy to get started, has a free 'community tier and integrates really quickly and easily into most UI projects. I use it daily at the moment and will be using it moving forward for all my client projects where they need a fully-featured, yet flexible CMS solution. For example, I use Astro and Storyblok integrates in under 5 minutes with no fussing or faffing.

The built-in datasources could be more useful if they allowed for tiered key relations. For example, if you need something like a country > city relationship using the built-in Storyblok datasources, you'll struggle. But this isn't a database, it's a CMS. The main blocker sometimes is the pricing. The community (i.e. free) tier is really great and very generous, but after this it's a large jump to the entry level pricing tier. This is oftern overkill for smaller projects or for some clients.

As a Jamstack-oriented web developer, my main focus is on providing great content experiences to clients' end users. One of the best ways to do this is via a platform like Storyblok as it allows clients to focus on their content and allows me to focus on consuming that content using the best technical means appropriate for the project.

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.

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.

Block componentes definition and console simplicity

Pricing is to high for workspace........

Content administraton flexibility

Among Storyblok's best features are its visual editor, spaces, stories, folder organization system, and workflow setup. It also has active customer support and a large developer community. The documentation is also very well written to cater to developer and non-developer needs.

The only downside is the unavailability of mutate/write access on its GraphQL API and a slightly steep learning curve in understanding the platform and configuring things like SSL for live preview and other integration.

Storyblok provides a central hub to manage my content, allowing me to define roles that provide certain levels of access to content and also define a creation-to-publishing workflow. It also simplifies the task of content management with its component blocks, and visual editor.

Storyblok is a fantastic CMS for Marketing and Content teams. The user interface is clean, very easy to use, and very intuitive. As a Product Designer myself, this is something I particularly appreciate. At the studio, we are big fans of the visual editor as it allows you to see the changes you’re doing in real time. This makes it very easy to build a page, adjust content, visuals, and components to get the exact results you need.

If you want to build something new on a page that hasn’t been developed (like a new block), you will need additional development support from a frontend developer. On the other hand, this means you are not restricted by any grid or pre-build layout, as you would find in other “web-builder” tool. You can go very custom when designing and developing something.

Storyblok provides a simple solution for our clients, usually non-technical users, such as content writers or digital marketing manager, who needs to build and maintain web pages. Again, the visual editor makes it effortless for them to review the page and see what it would look like exactly when published live.

It's a great CMS, easy to use. Very productive. Great free version, which is actually useable :)

Don't now any. Maybe a simulationius preview of different breakpoints at once?

Seperating content and development

It is indeed effortless to use due to the available components. It is also very easy to learn or to teach it to teams who have no prior knowledge about design.

The version two of Storyblok had some issues which are now being fixed. Other than that I am content.

Instead of paying an agency to help us with the website we can train people with no prior knowledge in web design in just a few days. We are saving money.

The preview feature is by far the platform's most impressive and helpful facet. But just as helpful are the drag-and-sort block reorganization, as well as the copy and paste features. We've reduced content population and new page creation by approximately 75% with these tools alone.

One downside is that it's not open source. So if our team wants to suggest a feature enhancement, we have to work through Storyblok's support, as opposed to just developing it ourselves.

A headless CMS that works with modern web frameworks and makes it easy for Marketing to own content. This allows us to develop highly optimized and secure websites for our clients, and makes it simple for our clients to manage the content themselves.

Storyblok is an awesome headless cms for any headless frontend. I love to use it for my personal projects build on Nuxt.js. I also plan to sell storyblok projects to customers in the future!

I took me a while to get into it but since i figured out the basic functionalities i am having a total blast!

It is hosted at storyblok and the community plan is one of the best i have ever seen. It is fast, easy to use and easy to develop on. Also the media library is highly benefitial.

Storyblok is very intuitive and easy to use from the for marketers. It give a great autonomy to handle pages and components. The preview is awesome and help us editing content fast. The Storyblok team answer to our questions quickly and they are very kind ans helpful.

I don't know if I really dislike something about Storyblok. I had some some bug on the first version, but second version seems to be very stable. Maybe it"s a bit easy to get lost when you begin to have a lot of blocks.

Storyblok helps us to give more autonomy to the marketing team. They are more efficient to handle contents on website. We can also choose preformant front end framework to offer the best user experience.

Storyblok is a fantastic CMS. I'm a big fan of the clean user interface and the way that sections of the system are organized. The usefulness of blocks in creating great looking pages that are easy to manage and manipulate is awesome. For sites with a lot of content, the search function is wonderful. Features like what's been most recently edited are also helpful. Overall a lovely editing experience.

Headless requires that a strong-front end developer has been involved in implementing a desired design. If you want to build something new on a page that hasn't been developed, it can require additional development support more so than in a drag&drop type system which may have more available out of the box.

Easy to find content for editing. Simple navigation and intuitive user experience for a CMS. Excellent ability to create pages and layouts using pre-defined options and systems for extending content across pages.