jmakowski1123
commented
2 years ago In progress with Kshitij at OC
Open jmakowski1123 opened 2 years ago
jmakowski1123
commented
2 years ago In progress with Kshitij at OC
jmakowski1123
commented
2 years ago May be a dupe of https://github.com/openedx/platform-roadmap/issues/144
arbrandes
commented
1 year ago The solution is likely to come about as a part of https://github.com/openedx/open-edx-proposals/pull/410.
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
Create a theming system that replaces comprehensive theming, in particular as it concerns platform-wide applicability. Start with the 5 currently supported Tutor MFEs.
Related work
David Joy started laying out the general problem in this draft OEP:
However, it has not been pushed forward.
OpenCraft has begun preliminary work on solution 1) via these two co-dependent ADRs:
David Joy has proposed work on an initial iframe-based extension system via this OEP:
Contingencies
The scope of this issue is limited to the Tutor-supported MFEs. A phase II can be implemented once XXX is complete and the remaining MFE conversions are completed.
This issue should be groomed alongside https://github.com/openedx/tcril-engineering/issues/423 and https://github.com/openedx/platform-roadmap/issues/24
Sub-tasks