Ondřej Chrastina
Menu
Content Editing Unlocked: Multisite, Visual Builder, and Editor Capabilities

Content Editing Unlocked: Multisite, Visual Builder, and Editor Capabilities

Conference talk at TYPO3 Developer Days 2026 in Karlsruhe, prepared together with Jürgen Pietschmann (T3Planet) and delivered solo. How to make content editing in TYPO3 maintainable across a multisite setup: shared RTE styles via Site Sets, custom icons that actually survive the trip to the live site, and CKEditor properly wired into the Visual Builder.

Back to talks
Released: Sat Aug 08 2026
  • Slides

What the session covered

Your editors deserve a consistent experience, no matter whether they work on one site or ten. This session was about making content editing in TYPO3 maintainable across a multisite setup - the configuration decisions that matter, the gotchas you only find in production, and what's coming in CKEditor that will give you even more control over the editing experience.

  • Multisite style configuration with Site Sets - defining style-based elements (buttons, callouts) via Site Set config.yaml and sharing RTE style presets across sites without duplicating config.
  • Custom icons inside CKEditor - the full pipeline from backend registration to frontend rendering, and what to check when icons show in the editor but not on the live site.
  • CKEditor in the Visual Builder - how Content Blocks and field types fit together, how to enable CKEditor for a Visual Builder field, with real TYPO3 v14 examples.
  • What's in TYPO3 now and what's coming - underused CKEditor 47.x features, CKEditor Plugin Pack news, CKEditor AI, and the upcoming paragraph-like editor model ($inlineRoot) for inline fields.

Takeaways

  • Decide how much WYSIWYG power your editors get, then build for that answer.
  • Share the editor configuration as a Site Set; sites opt in by dependency.
  • One component, one stylesheet, loaded in the editor and on the live site.
  • Icons and widgets follow the same rule: clean data attributes, rendered in both contexts.
  • When the editor and the site disagree, the bug is the contract between them.

The venue

TYPO3 Developer Days 2026, August 5-8 in Karlsruhe - the TYPO3 community's annual deep-dive event. CKEditor sponsored the event (we even had our own room). The talk was prepared together with Jürgen Pietschmann of T3Planet, but he fell ill on the first day of the conference, so I delivered the Saturday morning slot solo and took over his part about the Visual Builder, CKEditor Plugin Pack, and CKEditor AI.

Resources

  • Slides (PDF)
  • The "Content Editing Unlocked" repository (TYPO3 v14 demo)
  • CKEditor Pack for TYPO3 by T3Planet
  • Session page on the T3DD schedule
  • CKEditor issue #19921: paragraph-like editor configuration

Or scan them, straight from the closing slide:

QR code: the "Content Editing Unlocked" repository

The "Content Editing Unlocked" repository

QR code: CKEditor Pack for TYPO3

CKEditor Pack for TYPO3

  • Twitter
  • GitHub
  • LinkedIn
  • Facebook
  • Instagram
  • YouTube
  • Medium
  • dev.to
  • Discord
    • © Ondřej Chrastina 2020
    • Original Design: HTML5 UP
    • 💾 Source code - use GitHub issues for feedback 🙌
  • I am | Home
  • I write | Journal
  • I Code | Projects
  • I speak | Talks
  • PWA series
  • GitHub
Close