Single global/core theme for all networks/sites on a multi-network…
-
Hello,
I tried to search the web for any feedback on whether this is possible, or even advisable, but couldn’t find anything helpful in regards to a multi-network environment specifically… surprised?
I am using JointsWP/F6 as the global theme for all “properties” in my entire multi-site, and potentially multi-network. The template does not really support child-themes, and it is more work/trouble than it is worth, to try to hack it to…
So I have a different theme folder/version for every site. This is already cumbersome in multi-site, the current BETA environment is in shambles, not just because I am the lone guy in the corner coding (ref. your wptv clip), but because I am trying to maintain the same global code base across so many end points… cry me a river right?
But I was wondering if it is possible, and/or advisable, to try to set up the code environment so that it pulls from a single theme base, and all that each site houses is the granular unique ux functionality that it requires…
Before you just chalk this up to using a theme that supports child templates, the question remains whether or not using child themes at all is advisable across a multi-network on a macro level, which will obviously dig in really deep in terms of touch points on a micro level…
So based on my current scenario my tree looks like this…
wp-core-ms->(x)wp-site->(x)custom_theme
(x=number of sites)with multi-network it would look something like this…
wp-core-mn->(x)network->(x)wp-site->(x)custom_theme
(x=number of networks and/or number of sites)The way I envision it in my head is…
wp-core->global/core_theme->(x)custom_code_base->(x)network->(x)sitemaybe I am just going to far in the multi-network rabbit hole, and overthinking it…
Thoughts?
- The topic ‘Single global/core theme for all networks/sites on a multi-network…’ is closed to new replies.
