[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:  Awaiting
Component:  Themes                               |  Review
 Severity:  normal                               |     Version:
 Keywords:  good-first-bug has-patch needs-      |  Resolution:
  testing                                        |     Focuses:  ui,
                                                 |  administration
-------------------------------------------------+-------------------------

Comment (by helen):

 [attachment:"Screen Shot 2016-08-24 at 9.34.25 PM.png"] is a quick mockup
 of what I was imagining, which is an interstitial rather than a notice.
 Clicking the button would take you to the editor as it currently exists
 and the interstitial for editing a theme would no longer show for that
 specific user. Plugin editor should get the same treatment with its own
 separate user meta.

 The important things here are:
 * The right language in all of the messaging, including letting the user
 know that they won't see this message again should they continue on to the
 editor. My mockup is by no means a hard suggestion, although I think it's
 not so bad.
 * A resource (on .org somewhere? Codex?) that talks about custom CSS,
 child theming, FTP, and maybe even with a link off to something about
 version control. This would be the "learn more" link.
 * A parallel resource for plugins.
 * Visually emphasizing that this is very important to read, maintaining
 hierarchy and still looking good.

 Each of these items can be worked on separately, and if one wants to take
 a stab at a patch for the functionality of it, that is also a good start
 (although there should be agreement that this is a good approach).

 Reauth may be a nice add as well, but let's do this part first.

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