[buddypress-trac] [BuddyPress Trac] #6248: Add companion style support for the default WP themes

buddypress-trac noreply at wordpress.org
Sun Mar 8 16:31:40 UTC 2015

#6248: Add companion style support for the default WP themes
 Reporter:  Prometheus Fire  |       Owner:  hnla
     Type:  task             |      Status:  assigned
 Priority:  normal           |   Milestone:  2.3
Component:  API              |     Version:
 Severity:  normal           |  Resolution:
 Keywords:                   |

Comment (by boonebgorges):

 > 1. Less / SaSS - This has been raised before but feel we need to agree
 again whether we pre-process or not. Obviously we don't currently with our
 sheets, even though most of us will be working this way by default. IMO we
 haven't thus far, it may be a barrier to people getting involved, requires
 maintaining two files.

 My view is to use Sass. That's what core is using in the few places where
 it's begun to adopt a preprocessor. The slight increase in barrier to
 entry is easily offset by the increased modularity and maintainability.

 > Patches or Zip files: What is the best approach to working files and
 maintaining some principle of versioning? I have updated the current patch
 on the twentyfifteen and propose that as the base file we work from.
 Concerns are that with either approach we can stand to clash with multiple
 versions that then take additional time and work to resolve.

 I'm not 100% sure I understand the question, but I would suggest the
 following: Get your initial patch to a state where it's reasonably good
 and you are confident that you can complete it for 2.3, and then commit it
 to trunk. Then use smaller patches for ongoing development.

 > 3. Number of themes to tackle: I propose we tackle three initially as
 probably being the most we can manage and ensure a level of quality that
 we would wish within a release cycle

 I'd suggest we do as many as possible. At the same time, I would strongly
 suggest trying to get at least one or two completely done for 2.3 - better
 to ship with a really great stylesheet for Twenty Fifteen than to ship
 with half-done stylesheets for three different themes. So, maybe focus 50%
 of dev effort on twentyfifteen, 30% on twentyfourteen, 20% on
 twentythirteen; if the latter themes end up not being done in time, we can
 punt, while if the former ends up being finished, those resources can be
 devoted to the latter themes.

Ticket URL: <https://buddypress.trac.wordpress.org/ticket/6248#comment:10>
BuddyPress Trac <http://buddypress.org/>
BuddyPress Trac

More information about the buddypress-trac mailing list