Visual Editing in TYPO3: When Content Management Happens in Context

Camino was ideated and designed by Laura and implemented together with David and the Core Mergers. If you would like to delve deeper into the new features of TYPO3 v14, our session from Web Camp Venlo provides a good overview of the most important features.

But as exciting as many of these changes are, one of the most impressive topics related to TYPO3 v14 did not come directly from the Core in Venlo, but from the community environment.

Matthias Vogel, Head of Web Development at anders und sehr, presented a new way of content management in TYPO3 with the Visual Editor. The result is a practical, Core-adjacent extension that provides a first convincing answer to a question that has accompanied many editors for years: Why do we constantly switch between the frontend and backend when editing content?

Especially on pages with many content elements, the typical editorial routine often looks like this:

1. Open the page in the frontend
2. Search for the correct content element
3. Switch back to the backend
4. Find, open, and edit the corresponding element there
5. Save
6. Go back to the frontend and check if everything looks right

This process costs time, interrupts focus, and constantly pulls editors out of the actual context of their work. This is exactly where the Visual Editor comes in.

Via the “Editor” module in the new Content area of TYPO3 v14, a page can be displayed directly in the backend exactly as it will appear later in the frontend. Content is edited where it is visible: directly on the content element, with immediate feedback and without the constant switching between different views. The result is a true “What-you-see-is-what-you-get -experience“ for editorial work.

We are also very impressed with the consistently holistic focus on maintaining context. In the course of the changes for TYPO3 v14, “context” was repeatedly a key term: How do we create a backend that does not pull editors out of their work but keeps them as close to the content as possible? How can interfaces become tidier, more understandable, and more focused?

The Visual Editor provides a very convincing answer to this. Changes happen directly where content becomes relevant. Content elements can be repositioned via drag-and-drop, new elements can be added, and existing ones can be removed, and changes are visible in real-time without the page having to be reloaded. This creates a working mode that stays significantly closer to the actual editorial task.

Functionally, the solution is also remarkably advanced: The Visual Editor supports Workspaces, offers Auto-Saving if desired, can specifically highlight editable elements, supports Container Elements, and uses the new Context Panel for more complex editing steps—such as when replacing media content.

Especially noteworthy: The extension works directly with the new Camino theme without any additional effort. This is a double win. Anyone who installs TYPO3 v14 immediately gets a modern, cohesive frontend delivered with Camino. And anyone who also uses the Visual Editor raises editorial work to a new level.

This solution finally doesn’t feel like an isolated special path, but like a development that perfectly fits the direction of TYPO3 v14. Technically, the integration into custom themes outside of Camino is kept comparatively lean. Above all, the extension shows how much the preliminary work in the Core is now paying off. It creates a visual editing experience without separating itself from the system with heavy special solutions.

Normally, we tend to present our own solutions here. In this case, however, we were so impressed with the work of our colleague from Stuttgart that we consciously want to highlight it. Contributions such as this one show how much innovative power lies in the TYPO3 community—and how well Open Source thrives on good ideas being shared, tested, and developed further together.

For these reasons we want to say a big thank you to anders und sehr for this commitment to Open Source, which was directly adopted into the “FriendsOfTYPO3” cosmos.