In #3194414: Move Socialbase & Socialblue out of the Distro → we decided to contribute our themes to the community due to the following:
On our road to going decoupled, we want to make sure Open Social becomes available as a Headless product.
This means we have to move our Socialbase & Socialblue themes out of the Distro as they are not a necessary dependency for this product.However, as we are promising an out of the box featured community solution we want to make this front-end still available for those users who don't want to use our headless back-end.
Unfortunately this strategy has been postponed for the time being, and we're noticing a couple of things that aren't helping the product.
1. The themes are coupled to our Distribution, it's hardly a contributed theme that can be used without Open Social
2. Maintenance increases with it being separated from the Distribution
3. Changes are made independent from our code changes, making it more difficult to do proper QA over changes and communicate changes in our features. For example if we want to move to SDC (single directory components) changes made in moving things from our theme to our components would be easier to differentiate.
1. Stop support for
https://www.drupal.org/project/socialblue →
and
https://www.drupal.org/project/socialbase →
2. Add composer replace for both, making sure that if you have the themes added to your composer, it understand we're shipping the Distribution with it again and our version overwrites yours
3. Release a new (final) version for both themes and use that version to add the themes in 13.0.0 of our Distribution
4. See if we still need to backport changes back in to our themes in a new version for support of the themes in 12.x of the Distribution
Active
12.0
Front-End
This will be done in 13.0.0. The work is ready not yet in a tagged version, once that lands I'll mark this as fixed and we will stop supporting both themes on drupal.org