[buddypress-trac] [BuddyPress] #4953: BuddyPress specific UI refresh

[buddypress-trac]

#4953: BuddyPress specific UI refresh
-------------------------+------------------
 Reporter:  karmatosed   |       Owner:
     Type:  enhancement  |      Status:  new
 Priority:  normal       |   Milestone:  1.8
Component:  UX/UI        |     Version:
 Severity:  normal       |  Resolution:
 Keywords:               |
-------------------------+------------------

Comment (by boonebgorges):

 > with the legacy template files having got out in the wild any changes
 made to template markup and or styles could impact sites based on
 modifications of those, or is there a mechanism proposed that switches i.e
 not been aware of this 'plugin' aspect for packs or how that work, select
 plugin pack one wants and activate?

 It hasn't been 100% decided, but, like you, I'm very wary to make any
 changes to the in-the-wild bp-legacy templates that will break existing
 implementations. There are many things that we can and probably should do
 to the existing templates - since they were ported over pretty much
 directly from bp-default, and lord knows that there is much to be improved
 about bp-default's markup - but we shouldn't, for example, change the
 names of CSS selectors. Any "modernization" that is truly substantial -
 say, reworking the whole thing to use HTML5 elements - should be done in a
 separate template pack.

 > have almost finished re-factoring the /members/single/*.* templates to
 use the newer bp_nav_menu()

 Awesome. This might need to go in a new template pack, unless
 `bp_nav_menu()` outputs the exact same markup as the old function (I
 haven't checked).

-- 
Ticket URL: <https://buddypress.trac.wordpress.org/ticket/4953#comment:4>
BuddyPress <http://buddypress.org/>
BuddyPress