-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create a theming system that replaces comprehensive theming for the current Tutor-supported MFEs #418
Closed
1 task done
Labels
epic
Large unit of work, consisting of multiple tasks
Comments
This was referenced Aug 15, 2022
In progress with Kshitij at OC |
May be a dupe of openedx/platform-roadmap#144 |
The solution is likely to come about as a part of openedx/open-edx-proposals#410. |
I think it's safe to close this. The customizability story is well under way with plugin slots, design tokens, and the upcoming MFE modularity work. |
github-project-automation
bot
moved this from Backlog
to Closed
in Frontend Working Group
Nov 18, 2024
github-project-automation
bot
moved this from Backlog
to Done
in Axim Engineering Tasks
Nov 18, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 #423 and openedx/platform-roadmap#24
Sub-tasks
The text was updated successfully, but these errors were encountered: