Storyblok

The content model. It's simply unrivaled and what I always wished for.

- Every other CMS our there still wants me to assign specific named fields for a content type instead of letting me use blocks of well-defined structure in a hierarchical way within a content item.

- There are not only collections of types of content, but an actual hierarchy.

I wish there were more convenient ways to query *all* content items in a way that includes Caching.

The grapthQL API

- is not cached (as far as I know)

- does not let me query different content types at once (when searching for fields that all of them still may have in common)

A typical corporate content thing.

We absolutely love the editor experience, it is a breeze to get used to and learn to use, the plugins system makes it extremely powerful and we are very happy to use it on a daily basis for a dozen of sites!

The only missing piece we currently have is to have an additional "databases" or "collections" concept which could allow us to store and manage structured data in a headless way with the same awesome editor Storyblok offers, currently we have to store this data in another CMS and have the consuming application load data from two sources.

The difference to what is currently offered could be that instead of treating everything as "pages" and "components" you could also add arbitrary collections of "person", "product", "venue" etc and then use those just like you do datasources. (perhaps making datasources a bit more powerful?)

Don't think too much about it, give it a try and you'll absolutely love it!

Storyblok brings an unprecedented level of flexibility and control to the Headless CMS scene. Before we started using it, using a Headless CMS seemed like a great alternative for simple sites or sites with a clear structure.

Storyblok allowed us to unleash the creativity of our editors and site managers by letting them see the content changes in place, a familiar experience to many webmasters.

The Headless nature of Storyblok made it easier for us to repackage the content for different distribution channels with ease, which was mind blowing! :)

The best thing about this tool is available online, You can write & update your content while traveling and doing other stuff. They have every feature to organize content with your team and make the best website.

Nothing is bad on storyblok tools, but interface and design should be better for best use and give us more seats in the free version.

Yes, you can use it if you have a team and need every content organize. I suggest use free version and then you can buy paid.

I and my team of writers writes content for my organization and everything things are updated here, Any story, quote, or tagline, I can access written by my team, So it actually helps me a lot to connect with them all the time even while traveling. I mostly use a visual editor for a better approach towards customers.

It is incredibly good to work with:

Editors love the visual editor and the freedom to change content within seconds, developers love the component structure and the helpful team behind Storyblok.

We would love to see a customizable naming of the components for the editors.

We are developing enterprise-scale websites with Storyblok and Netlify. Now our clients have got a future-proof web development architecture. The benefits are top performance, scalability and ease of use for the businesses. Our clients do save $ in comparison with CMS solutions like AEM without compromises on their product website.

It’s the full package that works so well for me, Storyblok feels like a well thought out and complete product.

As a developer I love how it easily allows me to build complex structured and related data but for a content editor they can use a visual editor and see their changes quickly and easily.

The API is easy to work with and outputs JSON so can be consumed and transformed as needed using whatever technology stack you’re comfortable with - Vue, React, Laravel etc.

Headless CMS’s clearly are the future, decoupling the content from the frontend makes so much sense. So often a website suffers because the frontend is so tightly coupled to the content management system that upgrading it means upgrading everything. With a headless CMS you can freely replace the frontend whilst retaining the existing backend or push the same content to multiple channels.

The team is fantastic too, iterating and improving the product with new features and always friendly when offering support.

I can’t think of any major issues. There was a bit of a learning curve about how to best consume the API and structure content but nothing more complicated that any other CMS.

I’ve used and made a lot of content management systems over the years and they’re all suffered from similar problems. They either lack the flexibility to create the desired content structure, are very cumbersome to use, become ‘plugin hell’ with a mishmash of varied GUIs and duplicated functionality or are very hard to update.

Storyblok solves all other these issues. You build any schema you want for your data using a range of fields such as images, richtext, relationship links, or create your own VueJS based plugins. The interface is very clean and simple to use for editors - much of it takes place in the visual editor that allows content editors to see changes swiftly. As it outputs JSON you are free to totally change the website when updating without the usual migration headaches.