-
Notifications
You must be signed in to change notification settings - Fork 4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Making it easier to transition to Gutenberg #7060
Comments
"Edit" opens in Gutenberg; "Classic Editor" opens in the Classic Editor. You can convert a page/post from Classic to Gutenberg. Not a bug - that's by design. |
Three different areas: Frontend:Current: Can be: Notice the classic editor edit option. All Posts/All Pages:Inside a post or page:Current: Can be: Notice the Classic Editor option inside the drop down. Inside the TinyMCE content editor: Notice the Gutenberg tab. Notice the Gutenberg tab wording is now changed to the word Edit. The above creates a better integration of the Classic Editor and Gutenberg. Making it a lot easier and softer to transition to Gutenberg. Gutenberg really needs a long transition. For there will very likely be a lot of sites out there that have used TinyMCE in custom ways. |
Flagging as |
For now let's not do this, we won't be shipping with 2 editors when 5.0 happens. In that light lets close this. |
I noticed when activating Gutenberg then going to the frontend and clicking edit post/page that Gutenberg becomes the default editor. I thought the frontend would add a link to where one could choose to edit the post/page with the Classic editor or Gutenberg. (Similar to the Add New drop down button next to post/pages.)
While in the Gutenberg edit screen I see now way to switch over to the Classic Editor. I expected to click the top right 3 dots, and in the drop down and have the option to switch over to using the Classic Editor.
The text was updated successfully, but these errors were encountered: