[wp-trac] [WordPress Trac] #12423: Include default code editor

[WordPress Trac]

#12423: Include default code editor
-----------------------------+----------------------------
 Reporter:  scribu           |       Owner:  afercia
     Type:  feature request  |      Status:  assigned
 Priority:  normal           |   Milestone:  4.8
Component:  Editor           |     Version:  3.0
 Severity:  normal           |  Resolution:
 Keywords:  close            |     Focuses:  accessibility
-----------------------------+----------------------------

Comment (by jorbin):

 Replying to [comment:95 melchoyce]:
 > My concern is primarily around improving the CSS Editor in the
 Customizer. It is, quite honestly, a painful experience currently. Going
 between writing some CSS on WordPress.com and writing some on my self-
 hosted sites is not fun. The mockup here:
 https://core.trac.wordpress.org/attachment/ticket/38707/customizer-
 css-i2.png is very clearly an improvement on the existing CSS editor in
 core. It makes CSS easier to read, write, and maintain.
 >
 > Anecdotally, Jetpack's CSS editor is something I constantly recommend at
 local tech community project nights, where the vast majority of people I
 help tend to be beginners making WordPress websites. They're generally
 either currently learning, or already comfortable with, CSS. I'd like to
 be able to recommend using core's CSS editor, but I can't, because it's a
 significantly worse experience. I'd like to be able to use it for myself,
 instead of immediately reaching for Jetpack.
 >
 > Having a way to edit CSS in core is waaaay better than nothing, but it
 needs to be improved.

 Having just used the CSS editor on a site, I agree that it's far from an
 optimal experience. I also agree that when I chat with end users and site
 builders, it's something they find beneficial (but not super easy to use
 without some more advanced knowledge).

 Just looking at the text field piece of that mockup (and ignoring the
 interaction enhancements), it seems there are two components that set it
 apart from what is there now: Line numbers and syntax highlighting. Is
 that correct?  if so, those two things could be looked at separately and
 we might be able to find accessible ways to implement both.

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