[Project] Decouple HC from BuddyBoss

[mikethicke]

Description

The aim of this project is to move the Humanities Commons base sites off of BuddyBoss and our boss-child child theme in favor of a modern theme (tentatively 2023). Upon successful completion, the boss-child theme will be retired while retaining all of the current functionality.

Background

Humanities Commons is a "multi-network" WordPress / BuddyPress site, meaning that there are not just multiple individual WordPress sites run from the same instance, but multiple "networks" of sites. Each network is composed of a base site and user sites. The networks are:

• Humanities Commons (base site: hcommons.org, user sites *.hcommons.org)
• MLA Commons (base site: mla.hcommons.org, user sites *.mla.hcommons.org)
• ARLIS/NA Commons (base site: arlisna.hcommons.org, user sites *.arlisna.hcommons.org)
• HASTAC Commons (base site: hastac.hcommons.org, user *.hastac.hcommons.org)
• AUPresses Commons (base site: up.hcommons.org, user *.up.hcommons.org)
• SAH Commons (base site: sah.hcommons.org, user *.sah.hcommons.org)
• MSU Commons (base site: commons.msu.edu, user *.commons.msu.edu)

Each of the base sites uses the boss-child theme, which is a child theme of BuddyBoss (v. 2.2.2).

The core Humanities Commons functionality is spread across three plugins in addition to the boss-child theme:

• humanities-commons --- activated network-wide, on all base and user sites. Core functionality required for all sites goes here.
• hc-custom --- activated on base sites. Functionality specific to base sites goes here.
• humcore --- activated on base sites. Implements functionality for Fedora-based CORE repository.

(Additionally, the commons repository contains the base file structure of the site and must-use plugins that facilitate, for example, user authentication and domain mapping.)

The hc-custom plugin will be the plugin where most functionalities in boss-child are re-implemented. For functionality specific to the repository, changes should be made to the humcore repository.

Required Functionalities

The base sites have four central components:

1. Profiles (/members)
2. Groups (/groups)
3. Sites (/sites)
4. CORE Repository (/core)

A catalog of functionalities for the sites can be found here (Google Docs). To the extent possible, all current functionalities should be preserved.

To Do

Main Epic: #534

Sub-epics & issues:

• Groups functional on decoupled site hc-custom#177
  • Filter group listing by society groups and my groups hc-custom#171
  • Groups listing should have regular avatar hc-custom#175
  • "Create Group" link on main groups page hc-custom#172
  • Groups should have a badge or other indication of what organization they belong to hc-custom#173
  • Public / Private / Hidden / Managed (Committee) group types function properly. hc-custom#174
  • Organization groups should appear on groups listing page hc-custom#176
• Profiles functional on decoupled site hc-custom#178
  • Larger avatar on profile page hc-custom#180
  • Profile should indicate organizational memberships hc-custom#181
  • Profiles should display correctly on organizational commonses hc-custom#182
• Sites should function on 2023 theme hc-custom#184
  • Sites should have badges or other indication of organization hc-styles#8
• Humcore plugin functions with 2023 theme humcore#207
  • Welcome page does not display on 2023 theme humcore#203
  • Deposit page should function on 2023 theme humcore#204
  • Deposits page should function on 2023 theme humcore#205
  • Individual deposit view page should function on 2023 theme humcore#206
• Other
  • Users can register on all organizational commonses hc-custom#183

These should all function on all base sites.

Target Timeline

• Production release: 08-01
• Production-ready: 06-30
• Testing complete: 06-15
• Ready for testing: 06-01

Responsibilities

Development Lead: Mike
Main Developer: Dave
Community Lead: Bonnie