Features of the high-performance headless CMS "Storyblok"
In recent years, headless CMS has been gaining attention in the field of web development. I would like to introduce "Storyblok", which has been attracting attention for its high functionality.
Storyblok's capabilities have also been highly evaluated in Gartner's Customer Choice survey. Among the many headless CMS options available, Storyblok was the only service chosen.
Storyblok is pronounced "Storyblock", but the reason why it is spelled "Blok" instead of "Block" is because the CEO himself mentioned at an event that they were unable to secure the domain.
Now, Storyblok has gained support from many companies and developers who appreciate its convenience, as it offers more than just the basic features of a headless CMS and reaches the itchy parts that a simple headless CMS cannot reach.
Realize with Next Generation Web Manual!
~Build Management and Update Flow with Modern Frontend x Documentation~
I would like to introduce two features of Storyblok.
- Table of Contents
Storyblok Feature 1: Visual Editor
First of all, one of the biggest features of Storyblok is its built-in visual editor. This makes it very easy to preview content. Simply by specifying the URL, you can have a real-time visual preview and immediately see any changes made.
The preview screen is displayed prominently in the center of the screen. The right side of the screen is the editing screen for 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 between tablet and mobile views with just one button. Being able to check in real-time without having to save or deploy edited information is a major advantage.
To do this, specify the URL for preview, but it is also possible to specify it on localhost, which is a major advantage for smooth confirmation work even on a site under development.
Storyblok Feature 2: Block Library
Next, there is a componentized page part management function. This allows you to manage each part used in the page as a component and flexibly construct the page. In addition, by using the block library, you can customize and extend it according to the requirements of various projects. The process of registering elements that make up the page as blocks and combining them to create a page greatly contributes to the efficiency of development.
You can combine elements that make up a page within a template. For example, let's say there is a landing page for a campaign. That page would be composed of the following elements:
•Title Text
•Subtitle
•Catchphrase
•Title Image
•Logo
•Contact Button
•Call to Action Button
By preparing a page that combines these elements, you can edit the content of these blocks or rearrange and combine the structure of the blocks from the CMS management screen. And on the programming side, by defining only the main elements of the page, editors and designers can manage the content with a considerable degree of freedom regarding the elements within the page. For example, the site can be designed without the need to borrow the hands of 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 websites that constantly need to add new content. For example, even for an E-commerce site with a large amount of product information, its powerful CMS features can be easily utilized. The Nordic apparel giant Marc O'polo is often featured as a case study at Storyblok events, but when you actually check their website, you can see that the customization of pages such as product pages is very advanced.
Storyblok has these features, making it suitable for creating highly componentized pages, as well as for quickly creating LPs and campaign pages. It is also suitable for creating content that is prone to becoming outdated, such as technical documentation, as it allows for easy version updates. If content updates are frequent, it is very convenient to be able to immediately see how the content being edited in real time will affect the page. The high degree of freedom in combining page elements through the block library also contributes to its high satisfaction.
On the other hand, in cases where Storyblok is not suitable, it may be more efficient to use a simple static website generator instead of a high-functioning CMS like Storyblok, such as for creating one-time events or campaign sites in a short period of time. Additionally, if all that is needed is a database to store content, it may be better to choose a different headless CMS.
Summary
We introduced the visual editor and block library, which are the major features of Storyblok. Of course, Storyblok also has basic functions as a headless CMS, and can be used as a platform for delivering simple content. However, by utilizing these features in projects where they can be utilized, you can take advantage of their superiority.
At Storyblok, there are many other features such as collaboration within teams and ease of use on various front-ends. These functions and services will continue to evolve in the future. If you are considering implementing a headless CMS, why not consider Storyblok as one of your options?
Realize with Next Generation Web Manual!
~Build Management and Update Flow with Modern Frontend x Documentation~
Return to the top of the page
+81-3-5321-3111[Tokyo]
Contact Us
Resources
