WordPress.org

Make WordPress Core

#43888 closed enhancement (invalid)

Move Gutenberg editor to customize.php and leave / keep old editor

Reported by: alexvorn2 Owned by:
Milestone: Priority: normal
Severity: normal Version:
Component: Editor Keywords:
Focuses: Cc:

Description

I don't know if this idea was suggested before so I think Gutenberg feels better on customizer page instead of replacing the editor.

I made an image as example how it should feel:
check the attachment...

Attachments (2)

gutenberg-customizer.png (150.4 KB) - added by alexvorn2 14 months ago.
t
gutenberg-customizer-2.png (244.2 KB) - added by alexvorn2 14 months ago.
t2

Download all attachments as: .zip

Change History (4)

#1 @alexvorn2
14 months ago

check the second image! looks more elegant.

#2 @pento
14 months ago

  • Keywords 2nd-opinion removed
  • Milestone Awaiting Review deleted
  • Resolution set to invalid
  • Status changed from assigned to closed
  • Version trunk deleted

Thanks for the feedback, @alexvorn2!

If you prefer the old editor, check out the classic editor plugin, which will be the offical tool for restoring the old editor, if you need it.

I absolutely agree that Gutenberg fits well into site customisation, check out this talk by @melchoyce about the next phase of the Gutenberg project.

It's also worth remembering that WordPress 5.0 won't be released until it's ready: that means the block editor is a great experience, there are solid paths for upgrading your existing code to work with it, as well as reliable fallbacks to the classic editor when needed.

I'm closing this issue as Core Trac isn't really the place to have this discussion, but I encourage you to test your existing code and sites with the Gutenberg plugin, and report any bugs you run into over on the Gutenberg issue tracker.

Note: See TracTickets for help on using tickets.