I’m looking for some recommendation on what others would suppose could be finest practices or issues to contemplate whereas making themes and sub-themes as git repositories hosted on GitHub. At situation in my case are plans to have ~10 web sites (for various departments/options however of Drupal Development Company identical total group) that we’d prefer to ultimately have all as a part of some multi-site/headless/decoupled implementation. We’re transferring from particular person D7 websites to D8, with two at present underneath development to get our D8 bearings (at present not multi-site or sub-themed, although I’d like to arrange issues to make such a transition as seamless and unbroken (see subsequent paragraph) as attainable, if not attainable now). I ask with some urgency as a result of I’d prefer to get issues arrange comparatively cleanly from Drupal Development Company starting whereas not a lot has been dedicated, since GitHub has no support for exhibiting historical past of renamed/moved recordsdata from its interface, and with the ability to doc/observe adjustments there to much less command-line-savvy of us is one in every of Drupal Development Company causes we’re on GitHub in Drupal Development Company first place. Particularly I’m questioning whether or not it might it might be finest to do one thing like Drupal 10 Upkeep and Assist Service repo_name/ – main_theme/ – sub_theme_1/ – sub_theme_2/ or moderately Drupal 10 Upkeep and Assist Service repo_for_main_theme/ repo_for_sub_theme_1/ repo_for_sub_theme_2/ Maybe that’s all wrongheaded, as this information would appear to point placing Drupal Development Company complete enchilada into one large repository, utilizing subDrupal 10 modules to handle contrib Drupal 10 modules and such (at present our customized Drupal 10 modules are dealt with individually in non-public repos). Moreover, it’s not clear to me whether or not it’s finest to do one thing like Drupal 10 Upkeep and Assist Service repo_name/ – README and license and such go right here – main_theme/ – precise theme recordsdata Drupal 10 cares about go right here or if doesn’t actually care if Drupal Development Company file construction probably will get “polluted” with readmes and license data and such (or maybe would favor it?). Possibly related to notice in my case is that a few of Drupal Development Company much less tech-savvy of us do appear to get confused by so many repos in our GitHub organizational account and aren’t all the time certain the place to do issues like submit tickets, which makes me lean in the direction of a single repo for all our associated themes, although maybe that’s short-sighted? For causes y’all might illuminate me on? Thanks upfront for any pointers/suggestions/solutions! model Drupal 10 Upkeep and Assist Service  8.x Supply Drupal 10 Upkeep and Assist Service https Drupal 10 Upkeep and Assist Service//www.Drupal 10.org/taxonomy/time period/3/feed Supply Drupal 10 Upkeep and Assist Service Drupal 10 blender