Following the recent release of the new editor, we will be releasing the ability for users to migrate existing pages from the old editor to the new editor. We’ve been responding to the user pain from split-brain (having two editors in the same instance), and have been working on providing ways to create one unified editing experience through page migrations.
This feature will begin rolling out on February 20, 2020, to the Ecosystem Beta Group first.
This feature will allow users to migrate a page from the old editor to the new editor on a page-by-page basis. In addition to converting the page, this feature consists of a few main functionalities:
Preview page conversion
See the page in its converted state prior to actually converting the page. The modal will also notify you of the page’s eligibility.
Status of page eligibility
View the page’s content eligibility status in the footer as well as the modal.
- 100% eligible: content can be converted to the new editor with no data loss
- Ineligible/unsupported content: some elements are not supported in the new editor
- Collaborative editing: someone is actively working on this page
View unsupported content
Unsupported content will be highlighted in a yellow warning panel with a preview to what part of the content is unsupported (e.g., nested body macros). Since the remainder of the content is eligible, this allows the page to be converted with a warning consisting of a preview to the ineligible content.
Revert a converted page
If the user is not satisfied with the migration experience, they will have the ability to revert the migration to the old editor by reverting to the previous version.
Last but certainly not least, we will also be offering early access for those who wish to test their apps with this new feature. If you are interested, you can sign up here and provide information about your development/testing instances for early access.