Develop a plug-in system that closes the gaps where the custom theming system does not cover the extent of comprehensive theming flexibility

[jmakowski1123]

Problem

The MFE theming and branding methods are not compatible with comprehensive theming. “It was something that we all kind of agreed on and now we are completely ignoring it.” This has a direct and negative impact on provider clients, as each customer may require different branding and modifications.

Product/Platform Value

Allowing for simple across-the-board theming and extensibility has a direct impact on adoption: the easier it is to do, the more users the platform will have.

Acceptance Criteria

Related or in-progress work

Contingencies

Must complete #418 first.

[brian-smith-tcril]

It's not clear to me how this differs from #430 and #429

[arbrandes]

@brian-smith-tcril, yeah, there's significant overlap. For now, if you're interested in reading up on the main ideas for plugins, I would look at the "Related or in-progress work" in #429.

[arbrandes]

Another duplicate of openedx/platform-roadmap#27. The original intention was to have a more engineering facing ticket, in contrast to the product-facing roadmap one, but we opened the engineering tickets prematurely: we have yet to define what we should actually do, and are holding a summit at the end of the month to do so.