Storyblok Reviews & Product Details

The preview can let content writer easy to update & pusblish content. The product design is very smart and flexible to use.

The new pricing plans is too expensive! I will think about other solution if it force to migrate to the new plan.

Quick edit & preview content.

Love the visual editor, great discord community that's always willing to help.

Version 2 still has some issues that are being resolved, but I'm sure with time they will have them all worked out. I find myself jumping back to version 1 from time to time.

I was looking for a headless CMS with an easy to use visual editor, and Storyblok has definitely been a great solution for that. Our marketing team has no problem creating new landing pages, adjusting layouts, etc. with confidence that what they see is what they will get.

I think it is user friendly and user interface.

Missing the function of being able to clon in fields that can be done in Advanced Custom Fields in WordPress.

That it is visible to see what is edited is a Game Changer for our customers.

The preview functionality in the UI is very helpful when layouting a page and testing to see what all different components does. The preview image for components for images is also very helpful.

There are some basic stuff iImiss when creating and reusing fields. For instance there is no way at the moment to set a minimum amout of requierd fields, only a maximum. I would also really like a way to reuse componet-groups without having to use the block-field. When pointing out different bugs and suggestions for improvments the response on the offical forums is very slow.

When using a Gatsby as a frontend that is a generated static site the preview is very useful as the updates doesn't go live right away.

Storyblok is a pleasant experience for my clients. It creates a clear separation of concerns and since it is a paid service, clients do not have to deal with backups, updates, etc. which often is more expensive in the long run and creates all sorts of problems.

I think some of the data modeling could be more streamlined and more advanced input validation would be helpful for the content creators. Also there is usually the need of global fields for e.g menu items and configuration, so some dedicated options for such would be great.

Storyblok creates a streamlined experience for the client. Since it is a service I do not have to deal with the whole CMS hosting part as a dev. So no updates, backups and general server administration. This is beneficial for the client and I had good experiences, especially with smaller clients who normally are tempted to use solutions like WordPress which often creates a lot of headaches.

Content types and "bloks" pattern is used out of the box. It makes it dummy simple to build a dynamic site around SSR tech like NextJS and have it be highly optimized.

The release/branch/versioning pipeline is not user-friendly at the moment. It isn't intuitive to develop with nor is it to release as a content editor. Preview mode could also be setup to be a little clearer and easier to use. Explaining the URLs in preview to a content person and this release pipeline has been our greatest struggle. Additionally, out of the box auto-generated typings for TS would be a nice DX improvement.

Content management.

Easy to use Good features Having many options

Limitations in a few things Not seeing the updates without saving

Building web pages without being a developer or programmer

Easy to be used for non tech folks, intuitive. Allows to preview the changes you are providing real-time and has a good system to track the process of the publication and in the new version it also enhances cross-teams collaboration.

The assets management still has a few opportunities and challenges to be tackled.

Building a website with flexibility and content management system.

it's customizable to meet your very own requirements regarding your website etc. though this requires resources and development, having the option to do so gives flexibility.

Lack of formatting options when it comes to texts for content, which should be a basic feature. E.g. creating a numbered list is not possible.

Because of the fact that it's a headless CMS, Storyblok gives you a maximum of flexibility and options in displaying the content with less restrictions

The ease of use integrating with Vue/Nuxt projects. The live view of content

No self-hosted option Would like some automation options to clone environments using pipelines

Much more user-friendly than most other headless CMS.

That it is cloud based so there is no installation required on servers. Also it is easy to get started and has a good community.

That it may be cost prohibitive to some areas.

A suitable content management system without the server management.

Especially with version 2 I line that the things I got used to stayed basically the same, while beeing improved to make functiobs more accessable.

Imhsrd ro say as a casual user for a microsite. Could be more functions fir microsites.

I can mamage my website eithout beeing an expert.

The whole flow for our users is great! Almost no need to have workshops explaining the CMS (unlike other CMSs we used in the past).

From a developers perspective * The routes on pages come without / and root pages get a / - can be troublesome when building statically. * The image serive could be easier to use combining the different "filters" like focal point, crop and sizing.

When building sites for our clients that need to be fast, easy to use and frontend framework agnostic.

The fast-paced workflow for creating new spaces and the possibilities to extend these spaces for full enterprise application requirements. The preview is simple to explain to customers/editors.

I don't like the integration of additional "apps". I think the functionality should be provided to all spaces. Also, I would like some configuration on the preview tab for editors/admins or other roles. E.g. not everyone should be able to change the structure of the components.

The headless CMS approach is a state-of-the-art architecture for web applications with content. Storyblok provides a lean and fast API to provide the content and enables different stylings for the same data structure.

The visual editor is by far the best feature

Occasionally saving in the visual editor won't correctly update to reflect content

Building an mvp for a product

- It's ridiculously easy to structure your content logically - Content types and hierarchies - easy to use for non techy types - super extensible - supports multiple content formats - will make your marketing team happy - developers enjoy it too - great built in security

As a developer I do wish certain features for power users were more readily available, or that we could perhaps set up more powerful content rules and have the tools in the app to enforce them.

Delivering top-quality content to various different channels in a unified manner. Using it as a headless CMS for my clients(Freelance web developer/designer)

The ease of getting started and ready to plug in to my project.

I didnt like all of the layout of the cms but that was more from an esthetic point of view.

I used it to learn about cms as a concept and foubd an excellet tutor in storyblok.

Storyblok in general offers an excellent user experience provided by a visual editor. The customisation options are impressive - almost every customer's dream can be realized. There is good support for multilanguage and internationalization.

If you want to fetch data from Storyblok, some queries and their nesting can be problematic. Some basic options (ex. blocking content from editing) need an app and purchasing a higher plan. Also, the support for Gatsby (especially gatsby-image) seems to be not fully covered.

Problems: Gatsby (especially gatsby-image) support, problems with some queries nesting. On the development side, there are some issues, but the benefit is the final user experience the customer gets.

- WYSIWYG preview, the preview is awesome. - Custom data strucutre. - Publish approval progress.

- Assets preview, can't the whole image in assets list (seems they have improve this in v2)

Easily to build a static webpage, it's easy for engineering and content to work together.

Self-hosting a CMS for a website can be painful when it comes to regular maintenance tasks - applying security patches, updating the database, and adapting your custom backend code to changed APIs. Using Storyblok as your 'content repository' you can avoid this hassle and focus on your frontend code without worrying about future backend upgrades.

Once your web project starts growing, you might soon reach a point where the feature set of the free 'Community' account doesn't cut it anymore. Going from 'free' to '90 Euros/month' ('Entry' plan) is not for the faint of heart.

Website Content Management. No setup, no maintenance, and a powerful editing interface out-of-the-box. Plus it's really easy to build your own content editing components based on Vue.js