[buddypress-trac] [BuddyPress Trac] #9193: New BuddyPress Standalone theme for buddypress.org

[buddypress-trac]

#9193: New BuddyPress Standalone theme for buddypress.org
----------------------------------+----------------------------------
 Reporter:  espellcaste           |       Owner:  espellcaste
     Type:  task                  |      Status:  assigned
 Priority:  high                  |   Milestone:  Under Consideration
Component:  BuddyPress.org Sites  |     Version:
 Severity:  normal                |  Resolution:
 Keywords:  early                 |
----------------------------------+----------------------------------

Comment (by SirLouen):

 According to the 6th November meeting, we must consider two things

 Deciding how the new theme will be made.  @vapvarun suggested using BuddyX
 while, @imath suggests @buddyvibes.

 AFAIK, the problem with block-only themes, is that they are untraceable,
 so basically 100% of the content will be over the database, which could
 not be on a repo, so it will be completely impossible to submit any
 changes or review anything except for people with direct access to the WP
 admin.

 Any of the sites in the WP Meta ecosystem are running a full Block theme
 because of this.

 Personally, I would rather choose the @vapvarun
 https://github.com/vapvarun/buddyx choice, moreover knowing that it's
 coming from him, which happens to have a good full code template
 structure, and we can have support from him, and even @imath contributed
 to it, I can only see advantages on this option.

 This said, about the https://meta.trac.wordpress.org repo committing part,
 I'm doing my research on multiple places to see if we could add some extra
 committer there, so we could have more flexibility in the near future.

 But for now, we hardly still have anything, maybe if there is consensus,
 we should start a fork from BuddyX and start the works for the revamping
 from there?

 About the themes, judging by the current structure it seems that there are

 [[https://meta.trac.wordpress.org/browser/sites/trunk/buddypress.org/public_html
 /wp-content/themes/bb-base|bb-base]] (parent)
 |
 ├──
 [[https://meta.trac.wordpress.org/browser/sites/trunk/buddypress.org/public_html
 /wp-content/themes/buddypress-org|buddypress]] (child)
 └───
 [[https://meta.trac.wordpress.org/browser/sites/trunk/buddypress.org/public_html
 /wp-content/themes/bbpress-org|bbpress]] (child)

 While codex subdomains (codex.bbpress.org and codex.buddypress.org), don't
 share the same parent, and they are completely independent (which they
 shouldn't IMHO). And finally, the @imath experiment in
 https://developer.buddypress.org which happens to have also, another
 theme.

 Ideally, we should be merging all (codex, developer, etc…) into the main
 domains, and put all the required templates according to them.

 Conclusion: First developing a new or adapting an existing theme (BuddyX)
 to a new bb-press parent theme for buddypress/bbpress new sites before
 looking at how it will be introduced in the sites. Anyway, I'm on my way
 of looking for more committer options, as I mentioned before.

 ** Some final notes:**

 1. If we choose BuddyX, since @vapvarun is the original dev of this theme,
 maybe he could fork this in GitHub into a "bb-base" new parent and start
 working from there?

 2. Considering that bbpress is moving into git docs, why not take
 advantage of this revamp and do something like:
 https://developer.wordpress.org/advanced-administration/
 https://github.com/WordPress/Advanced-administration-handbook/
 Git administrated docs with a front face into developer.b*press.org?,
 inside the newly selected theme?

-- 
Ticket URL: <https://buddypress.trac.wordpress.org/ticket/9193#comment:19>
BuddyPress Trac <http://buddypress.org/>
BuddyPress Trac