[wp-meta] [Making WordPress.org] #1015: DevHub: Better sass structure

[Making WordPress.org]

#1015: DevHub: Better sass structure
---------------------------+----------------------------
 Reporter:  atimmer        |       Owner:  kevinwhoffman
     Type:  task           |      Status:  assigned
 Priority:  normal         |   Milestone:
Component:  Developer Hub  |  Resolution:
 Keywords:  needs-patch    |
---------------------------+----------------------------

Comment (by obenland):

 I'd like to avoid setting up a protocol or guidelines for now and rather
 have it evolve organically.

 The existing Gruntfile encourages a similar setup as in the parent theme,
 so I think that'll come automatically. Components probably shouldn't move
 up to the parent until they're used by at least one other site. The
 downside of being to liberal with globalized components is not only bloat
 but, more importantly, unforeseen style changes. See the `wp4.css`
 dilemma.
 Once a component gets globalized, other child themes might have to be
 updated to exclude that component from their build tree.

 With the parent theme in place now, would you be interested in rewriting
 the devhub theme to use it?

--
Ticket URL: <https://meta.trac.wordpress.org/ticket/1015#comment:19>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org