I've been working on a default footer that is generic for Open edX, not specific to
edx.org.
Currently we have code in places like main.html that checks to see if theming is on, if so uses the theming template overrides, if not uses microsite's get_template_path which in term checks to see if microsites are used, if so uses the microsite template overrides and if not falls back to the original template name.
Rather than add yet another bit of logic to main.html itself, I thought'd I'd put the logic in microsites which immediately led to the question: why not put the theming logic there too.
Assuming that everywhere that checks for theming also checks for microsites, I'm proposing MOVING the logic that checks for theming and sets the theme template overrides INTO microsites.get_template_path.
Note I'm not proposing completely merging the notion of microsites and themes (yet) just containing all template overriding logic to a single place.
As a follow-on step, I could rename microsites as it's now a little more general. OR rather than calling microsites.get_template_path directly, I could move get_template_path out of microsites and have it just route to microsites if necessary. But that's a separate refactor.
Any concerns before I start working on a PR?
James