Side-by-side live preview and page content editing

TYPO3 Association Community Budget Ideas 2025 Q3
1

Idea Title

Side-by-side live preview and page content editing

What is my idea about? What is the problem we are solving?

We propose building a dedicated “Live Preview” module for TYPO3, combining functionality from the existing Page and View modules into a single, more intuitive interface with new features.

The current workflow for editing content and previewing changes is fragmented—users must switch between editing forms and frontend preview tabs. This slows down editing and makes it harder to manage content or translations. Our module aims to improve content editing and previewing (after saving in TYPO3 backend edit form) by providing a side-by-side interface with live preview.

What we want to achieve by the end of Q3 2025?

A new backend module that is combining page preview on the one side with page module.

Persistent preview: after editing or adding new CE and saving a CE, the updated content appears instantly in the preview pane.

Support for language-specific previews, favoring explicit language views (not combined/mixed).

Clicking on a content area in the preview opens the relevant CE editor while keeping the preview in view.

Note: In this first iteration, we will not support workspaces, gated content, start/end times, or frontend user group access.

What is the potential impact of my idea for the overall goal?

This idea will greatly improve TYPO3’s content editing experience—especially for editors, marketers, and translators. Inspired by solutions from systems like Storyblok or Sulu CMS, it will:

  • Eliminate constant tab-switching between edit and preview.
  • Offer a faster, more intuitive workflow for editing full pages.
  • Support translators and multilingual teams with focused language previews.
  • Lay a strong foundation for future expansion (e.g., workspaces or conditional visibility).

It will make TYPO3 more competitive with modern CMS platforms.

How does my Idea align with the strategic goals for TYPO3 v14.

Strategic Goal 2 — Reducing Complexity: Combines multiple backend views into a single, coherent interface, simplifying the content workflow.

Strategic Goal 4 — Improve Customer-Oriented Communication: Delivers a modern and intuitive editing experience for non-technical users.

Strategic Goal 3 — Enabling Better Content: Enhances the creation and management of multilingual content by enabling immediate visual feedback.

Which budget do we need for this idea?

10000 Euro

My Name

Tomasz Woldański

5 Likes
2

Note: In this first iteration, we will not support workspaces, gated content, start/end times, or frontend user group access.

From my point of view, this is a no-go; all core principles must be supported and should be part of the first considerations. Excluding basic core features will end up in incomplete features and will be a waste of money.

2 Likes
3

To clarify, I would like to design this feature with all TYPO3 core functionalities in mind. However, in the first iteration we will limit the initial scope of the side-by-side feature due to budgetary constraints. We are required to have a working version by the end of Q3. If everything goes well, I will try to implement as many core features as possible.

My goal is to overdeliver rather than overpromise. I believe this feature even if in limited scope will enhance TYPO3’s competitiveness in the current CMS market, and we should expand it together as a community. The feature will be available as a public extension and can be easily merged into the core if the core team approves when delivered.

4

Hi Tomasz,

first of all, thanks for submitting this proposal!

As you might know, a side-by-side preview is part of the official TYPO3 v14 roadmap, under the “Fresh Look & Feel” roadmap objective. Because of that, it’s particularly important that this work is coordinated closely across all relevant teams — especially the UX and core team — to ensure we’re aligned and working together effectively.

I also strongly believe it should be developed as a core component from day one — not as an extension. TYPO3 has seen in the past that solutions developed outside the core often struggle with long-term adoption and maintenance, simply because they don’t receive the same level of shared responsibility and visibility.

That’s why it’s essential to involve all teams from the very beginning. I’d be happy to help facilitate coordination — but as mentioned, I believe close collaboration is crucial to making this a success.

Thanks again — I’m looking forward to seeing how we can move this forward together!

Best,
Oli