[wp-trac] [WordPress Trac] #31779: Warn users before using a built-in file editor for the first time

[WordPress Trac]

#31779: Warn users before using a built-in file editor for the first time
--------------------------------------+---------------------------------
 Reporter:  helen                     |       Owner:  helen
     Type:  enhancement               |      Status:  reviewing
 Priority:  normal                    |   Milestone:  4.9
Component:  Themes                    |     Version:
 Severity:  normal                    |  Resolution:
 Keywords:  good-first-bug has-patch  |     Focuses:  ui, administration
--------------------------------------+---------------------------------

Comment (by melchoyce):

 Replying to [comment:46 cliffseal]:
 > 1. Move the Editor into the Tools menu, or into Tools > Available Tools.
 It fits better there anyway: it's not a visual editor for the
 ''Appearance'', as other things are in the Appearance menu), but the other
 problem with Plugins > Editor is it's right beside one of the most clicked
 buttons in the UI (Add New). It's too easy to discover. You could also
 move the warning messages suggested above into a box on Available Tools.
 Instead of a warning, it becomes the context for launching the Editor.
 Plus, what else is going on in that page anyway. :)
 > 1. To do the above, combine the Theme and Plugin editors into one.
 Separate the edit dropdown with headings for Theme and Plugins.

 Let's split this into another ticket (if one doesn't exist already), since
 it's worth considering on its own, independent of whatever we do here.

 FWIW, I mocked up a draft for what a post-Gutenberg code editor could look
 like in core. I think this design could work under tools, and includes a
 switcher between Themes/Plugins: https://github.com/WordPress/better-code-
 editing/issues/41

--
Ticket URL: <https://core.trac.wordpress.org/ticket/31779#comment:54>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform