While I think it is a nice setup. I would not call it a real time visual editor.
The preview method is the key to real-time editing. When editors make changes in Storyblok
You need to have two windows open to see the changes, that might be a hurdle for some people.
I know a lot of people will associate real time visual editor with drag and drop elements on the page where they then can add text, video, images or other components. And everything is in the final theming of the page.
I do agree with you that a headless CMS solution doesn't need a javascript frontend, it can be anything that can use the API calls of the solution.
PHP enthusiast, passionate about quality tools, AI exploration, and sharing knowledge through articles. Automation is my playground; I’m always learning, innovating, and pushing boundaries.
Thank you for the feedback. With the Storyblok Visual Editor, everything happens in the same window, so there’s no need to open two windows. In that single view, you have the tools to edit the content, and the frontend is loaded in the same window (via an iframe) as a preview.
As you apply changes—before clicking Save—you can immediately see the preview update. That’s why I describe it as real-time (technically, browser events trigger the changes).
While I think it is a nice setup. I would not call it a real time visual editor.
You need to have two windows open to see the changes, that might be a hurdle for some people.
I know a lot of people will associate real time visual editor with drag and drop elements on the page where they then can add text, video, images or other components. And everything is in the final theming of the page.
I do agree with you that a headless CMS solution doesn't need a javascript frontend, it can be anything that can use the API calls of the solution.
Thank you for the feedback. With the Storyblok Visual Editor, everything happens in the same window, so there’s no need to open two windows. In that single view, you have the tools to edit the content, and the frontend is loaded in the same window (via an iframe) as a preview.
As you apply changes—before clicking Save—you can immediately see the preview update. That’s why I describe it as real-time (technically, browser events trigger the changes).
I jumped too soon to the code, that is why I came to the wrong conclusion.