Visual Editing in TYPO3 v14: Hype or real need?

A few weeks ago, I sent out a survey. The question was simple: What do you think about Visual Editing in TYPO3 v14? Do you need it? For what? And what would stop you from using it?

The survey was sent to almost 800 former and active course participants. 39 of them took the time to actually participate. This is not a representative study and I am aware that the sample is small. Nevertheless, I want to share the results because the answers are consistent and paint a clear picture. Almost all participants work as integrators or developers, whether as freelancers, in an agency or in-house. In other words, the very people who implement TYPO3 projects and let their customers work with it.

Two thirds see a real benefit

Just under a third of participants said: "Very relevant, we would actively use it. Another third see it as helpful, but not a must. Around 13% are neutral, the rest see it rather critically or as irrelevant.

This is not hype. But it is a clear signal: the majority of TYPO3 professionals see visual editing as a concrete benefit for their projects.

It's a customer request, not an integrator feature

Unsurprisingly, but the figures clearly confirm it: 77% of participants see editors or project managers on the customer side as the actual users. Visual editing is not a tool that integrators themselves need on a day-to-day basis. It is a tool that they would give to their customers.

A good third of those surveyed have already experienced customer demand, sometimes several times. Agencies with direct customer contact report this in particular. On the other hand, 36% say that no customer has ever asked for it. Visual editing is therefore not a universal customer requirement. But where customers compare (especially with WordPress), it becomes an issue. And perhaps it's also a matter of getting used to it: once you've experienced how quickly text can be corrected in the frontend display, you may not want to go back to the classic page module.

Correct texts, swap images, done

There is a clear pattern in the use cases. 95% cite the adjustment of texts and headings as the main purpose. 77% want to be able to replace images directly in the frontend. A good half see moving content elements via drag & drop as relevant.

More complex scenarios, such as building landing pages or changing page structures, are much further down the list. So the need is clear: quick, simple corrections directly on the page. Not a page builder replacement. No paradigm shift. Simply fewer clicks for standard tasks.

The biggest concern: Will it remain stable?

74% cite "risk of updates and maintenance" as a potential exclusion criterion. This is by far the most frequently cited obstacle and tells a story that everyone in the TYPO3 community knows: Frontend editing has been announced several times. It has never really worked in the long term.

This mistrust is justified. And it means that the technical solution alone is not enough. It must remain stable across several major versions so that integrators can incorporate it into customer projects with a clear conscience.

This is followed by three further concerns, all of which are in the 50 to 62% range: Too much template customization required, performance overhead due to additional JavaScript and problems with multilingual sites. These are all points that directly affect day-to-day work. If visual editing creates more work than it saves, it will not be used.

What is really annoying about backend editing so far

18 participants answered the open question, and the answers are revealing.

Several describe the same frustration: too many clicks to navigate through nested content. Containers and accordions make the page view confusing. After saving, you end up at the top of the page instead of the element you just edited. The standard display of the content blocks looks, as one participant put it, "totally old school and dusty".

The real problem behind this: The abstract backend view is not an obstacle for tech-savvy integrators. But for editors on the customer side, there is no visual reference to the end result. The input masks are too far removed from the actual image of the website.

However, my experience from numerous editor training courses shows a different picture. If you explain the backend and the link between backend and frontend to editors properly, it is usually not a problem. I have even received feedback that the TYPO3 backend is actually very intuitive. The prerequisite: It must be configured appropriately for editors. Anyone who gives editors admin access is shooting themselves in the foot. The problem is therefore often not the backend itself, but how it is prepared for the target group.

Nevertheless, two participants go one step further and specifically report that they have lost orders to WordPress. The reason: the customers wanted frontend editing and found it at WordPress. This is not a theoretical scenario, but lost business.

Remarkable is the comment of a participant who manages over 400 websites in the municipal sector. The customers there are not particularly tech-savvy. Visual editing could make the decisive difference for precisely such scenarios.

Does the topic belong in a TYPO3 course?

A third of respondents want to see visual editing as a separate chapter in a complete course. Another third say that an overview is enough. Only 10% say it is not necessary.

For me, this is a clear statement. Visual Editing will have its own short chapter in the TYPO3 complete course: What is it, how does it work technically, for which projects is it worthwhile, and where are the limits.

My impression after the live demo

After the survey, I had the opportunity to see the current state of Visual Editor in a personal demo. I was skeptical. After the demo, I am at least curious enough to take a closer look at the whole thing in my own projects.

The biggest concern from the survey was stability during updates. And this is exactly where you can see that the developer has understood the problems of previous approaches and has deliberately solved them differently: The extension is built almost entirely on core functionality and contains very little custom code. This means that as the TYPO3 core evolves, the Visual Editor moves with it instead of working against it. And the goal is clear: integration into the TYPO3 core from version 15.

The integration effort is significantly less than expected. For an existing, larger project, the developer reckons with around four hours. Essentially, two adjustments are required in the Fluid templates: <f:render.text> for editable text fields and <f:render.contentArea> for content areas with drag & drop. If you use FluidStyledContent without your own template customizations, you have even less to do. And if you uninstall the extension again, you will end up with a project that works exactly as before. Nothing is broken.

The other concerns from the survey also look better than feared: Multilingualism is fully supported, so are workspaces, containers work, content blocks are fully supported. The extension is already running productively in several existing projects.

A detail in passing: the developer himself uses the Visual Editor on a daily basis as a replacement for the normal backend forms. Anyone who uses their own tool on a daily basis knows the weaknesses and has a real incentive to fix them.

Can I now recommend it with a clear conscience? Not yet. A demo is not the same as real experience in real projects. I will be testing the whole thing myself in the coming weeks before I can make a well-founded assessment. But the technical approach makes a well thought-out impression, the effort seems manageable and the risk low. That's enough for me to keep a serious eye on the topic and include it in my new course.

My conclusion

Visual editing will not be a feature that everyone will immediately incorporate into every project. The concerns about stability and effort are too great for that. But for agencies and integrators who want to offer their customers a contemporary editing experience, it will become a relevant tool.

The biggest hurdle is not the feature itself. It is trust. Will it remain stable? Will it still work after the next update? Is the integration effort worth it in the long term? If the TYPO3 community answers these questions well in the coming months, visual editing has a real chance.