[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 aaroncampbell):

 Replying to [comment:58 rmccue]:
 > 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.

 This is the part that worries me a little.  Currently the process is
 something like this (assuming you're using uncompressed CSS):
 1. See a problem
 1. Right-click, inspect element
 1. See that it's on line XXX of some.css
 1. Edit line XXX of some.css
 1. Test
 1. Create patch and upload to ticket

 It seems like we'd be turning it into:
 1. See a problem
 1. Right-click, inspect element
 1. See that it's on line XXX of some.css
 1. Track down what scss file creates that line (correct me if I'm wrong,
 but most built-in dev tools don't support tracking back to scss yet,
 right?)
 1. Edit line XXX of some.css
 1. Re-build some.css based on it's scss files
 1. Test
 1. Create patch and upload to ticket

 I'm afraid that steps 4 & 6 (the newly added steps in the process) are
 going to be the hardest ones.  Currently someone can learn almost
 everything they need to know to contribute a CSS patch just by tweaking on
 their personal site for a while (the one exception being generating a
 patch).  The new method would involve more tools that they can't learn in
 that way, causing a steeper learning curve.

 I'm not saying this isn't doable, but there's going to be more training
 needed and I think we need to seriously consider how this will affect our
 volunteer contributors.

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