Problem

There's quite a bit of duplication in the socialbase and socialblue gulp files. There's also some preview specific build steps in socialblue which may be required for sub-themes to function properly.

Proposed Solution

Split out the used build steps in Open Social to a separate package. This allows dependencies to be more easily coordinated across socialblue and socialbase. It also allows sub-themes to more easily re-use the required build steps which allows them to take advantage of improvements in the Open Social themes.

This opens up possibilities in the future where subthemes can be made smaller by only selectively replacing certain files using a custom SASS importer (https://github.com/sass/node-sass#importer--v200---experimental) and relying on the underlying theme's file for all other files.

That in turn can open up the possibility for layered styleguides where we can use a system that mimics Drupal's template inheritance (looking through the theme stack in reverse order and defaulting to the module's CSS).

Comments

Kingdutch created an issue. See original summary.

kingdutch’s picture

Issue summary: View changes

Add some additional advantages

bramtenhove’s picture

Kingdutch, am I correct to recall that you did this recently in https://github.com/goalgorilla/sweet-pea?

kingdutch’s picture

Version: 8.x-1.x-dev » 8.x-3.x-dev
Assigned: Unassigned » kingdutch

Yes but some more work is needed here. Sweet Pea is not quite ready to replace the current build tasks in socialbase/socialblue.

xinyuma’s picture

Version: 8.x-3.x-dev » 8.x-6.x-dev
kingdutch’s picture

Status: Active » Closed (outdated)

Themes have been moved out of Open Social