Created by: seanmadsen

So, we have a separate repository, civicrm-docs-material for the theme customizations which was part of my plan, but now I'm doubting this choice a bit, after talking with @michaelmcandrew today. I'd like some advice on the best way to proceed here, especially from @totten

The theme customizations need to be accessible (and current)

• (A): on www-prod when publishing books
• (B): locally for theme developers to use with mkdocs serve
• (C): locally for civicrm-docs developers after doing civibuild docs

So the question is, how do we store the theme customizations to best meet all these needs. Here are ideas that emerged from my convo with Michael

1. civicrm-docs-material as a git submodule within civicrm-docs
2. theme customizations stored within civicrm-docs directly (and we get rid of the separate repo)
3. something else?

I don't have an opinion. Do others? (Sorry if it was a bit premature to create that new repo and add 6 issues within it! 😬 )