[wp-trac] [WordPress Trac] #22862: Consider a CSS preprocessor

[WordPress Trac]

#22862: Consider a CSS preprocessor
-----------------------------+------------------------------
 Reporter:  chriswallace     |       Owner:
     Type:  feature request  |      Status:  new
 Priority:  normal           |   Milestone:  Awaiting Review
Component:  Administration   |     Version:
 Severity:  normal           |  Resolution:
 Keywords:                   |
-----------------------------+------------------------------

Comment (by rmccue):

 Replying to [comment:57 helen]:
 > Beyond making the files LESS/SCSS, what does the patching process look
 like for somebody? Like from figuring out where the problem CSS is to
 fixing it to making a patch and submitting it.

 We can generate source maps with Sass that will
 [http://bricss.net/post/33788072565/using-sass-source-maps-in-webkit-
 inspector give a reasonably good output] (and I think Less has similar).
 For production, we may want to minify the stylesheets, but otherwise, we
 can also output [https://gist.github.com/rmccue/6153632#file-buttons-
 css-L58 comments into the CSS] that point back to the source.

 To contribute a patch, they track down the source in SCSS/Less and fix the
 issue there, while running `grunt watch` or similar, which will
 automatically rebuild their CSS on the fly. Once it's fixed, patch as
 normal.

--
Ticket URL: <http://core.trac.wordpress.org/ticket/22862#comment:58>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software