Headless CMS has been attracting attention in the field of web development in recent years. Among them, I would like to introduce "Storyblok," which stands out for its high functionality.
Storyblok's capabilities have also been highly rated in Gartner's Customers' Choice survey. Among the many headless CMS options available, Storyblok was the only service selected.
Storyblok is pronounced "Storyblok," but the reason it is "Blok" instead of "Block" is simply because the domain name was not available, as the CEO himself mentioned at an event.
Now, Storyblok goes beyond the functions of a simple headless CMS, offering features that address even the smallest needs, and it is supported by many companies and developers who appreciate its convenience.
Achieved with Next-Generation Web Manuals!
~ Management and Update Workflow Built with Modern Frontend × Documentation ~
I would like to highlight and introduce two features of Storyblok.
- Table of Contents
Storyblok Feature 1: Visual Editor
First, one of the main features of Storyblok is that it comes standard with a visual editor. This makes it very easy to preview content. By simply specifying a URL, you can have a real-time visual preview and instantly see the changes.
A large preview screen is displayed in the center of the screen. The right side of the screen is the editing interface for the content and block CMS. When you add or change text in this right section, the changes will be displayed in real-time on the preview screen.
You can switch the display for tablets and mobiles with the push of a button. Being able to check information in real-time without saving or deploying changes is a significant advantage.
For this, you specify a URL for the preview, but since you can also specify localhost, it is a great advantage that you can smoothly perform checks even on sites under development.
Storyblok Feature 2: Block Library
Next, there is a componentized page part management feature. This allows you to manage each part used within a page as a component and build pages flexibly. Additionally, by using the block library, you can customize and extend according to the requirements of various projects. The process of registering elements that make up a page as blocks and combining them to create pages greatly contributes to development efficiency.
You can combine the elements that make up a page within a template. For example, let's say there is a landing page (LP) for a campaign. That page might be composed of the following elements.
• Title text
• Subtitle
• Catchphrase
• Title image
• Logo
• Contact button
• Call-to-action button
If you prepare pages by combining such elements, you can edit the contents of these blocks or rearrange and combine the block structures from the CMS management screen. On the programming side, by defining only the overall framework of the page elements, editors and designers can manage the content inside the page with considerable freedom. For example, the site can be designed so that there is no need to rely on engineers to rearrange the position of buttons.
When Storyblok is Suitable and When it is Not
Storyblok is a headless CMS with advanced customization and reusability, making it useful for sites that need to continuously add new content. For example, it is well suited to e-commerce sites handling large volumes of product information, leveraging its powerful CMS features. The major Nordic apparel company Marc O’polo is often featured as a case study at Storyblok events, and a review of their site reveals that the customization of product pages and other elements is very sophisticated.
Due to these features, Storyblok is well suited for cases where you want to freely manipulate highly componentized pages, need to quickly create landing pages or campaign pages, or produce content prone to obsolescence with version upgrades, such as technical documentation. If content updates are frequent, being able to immediately see how the content being edited in real time affects the page is extremely convenient. The high degree of freedom in combining page components through the block library also contributes to high user satisfaction.
On the other hand, cases where Storyblok may not be suitable include the creation of one-time events or campaign sites within a short period. In such cases, it may be more efficient to use a simple static website generator instead of a high-functionality CMS like Storyblok. Additionally, if all that is needed is a database to store simple content, it might be better to choose another headless CMS.
Summary
We introduced the visual editor and block library, which are major features of Storyblok. Of course, Storyblok also has the basic functionalities of a headless CMS and can be used as a standard platform for delivering simple content. However, by utilizing these features in projects that can take advantage of them, you can leverage its superiority.
Storyblok offers many other features, such as team collaboration and ease of use across various frontends. Its functions and services will continue to evolve in the future. If you are considering introducing a headless CMS, why not consider Storyblok as one of your options?
Achieved with Next-Generation Web Manuals!
~ Management and Update Workflow Built with Modern Frontend × Documentation ~
Return to the top of the page
+81 35-321-3111[Tokyo Headquarters] 
Contact Us
Resources
