Description
Summary
Prior to Page Builder, all rich content was managed with the TinyMCE editor. Essentially it is stored as constrained raw HTML and presented for visual editing. If we enable Page Builder then all legacy content is imported as HTML code. Given legacy content is just HTML that could be edited in TinyMCE, what has it not been imported as a Text element? What was the rationale behind this?
That way legacy content could continue to be managed as the single text block it was previously. Only if enhanced layout is required would it need to be extended in Page Builder. As it stands, we cannot enable Page Builder for existing sites because then all rich content would have to be reimplemented in Page Builder for non-developer end-users to work on it.
Examples
Enable Page Builder on an existing site that hasn't used it before. All rich content is now HTML code and effectively non-editable by end users.
Proposed solution
Import legacy content as a single Text element, allowing it be managed as previously.
Release note
Better support for switching from legacy TinyMCE to Page Builder.
Triage and priority
- Severity: S0 - Affects critical data or functionality and leaves users without workaround.
- Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
- Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
- Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
- Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.
Activity