| Info |
|---|
These are my (Kyle McCormick's) running notes as I do an investigation into the challenges that Open edX developers face when using Microfrontends and how we can address those. They represent my opinion and have not been approved or reviewed by any other edX employee. |
...
With the onset of the LMS courseware MFE effort, it’s become more apparent than ever that we are serious about rewriting its frontends, and not just the ones that are edX.org-specific. As time goes on, we will need to done do one of the following:
Continue to support all non-edX.org-specific Django frontends for Open edX instances.
Deprecate significant portions of Open edX frontend without any official alternative implementation, leaving it up to the Open edX community to figure out how to either run our MFEs or develop their own.
Officially make Microfrontends part of Open edX
...
No, in that MFEs are not included in the Native Open edX installation, which many small Open edX rely upon.
...
So what do we need to do?
TODO: Flesh this out
Based on the above, I see three categories of work to be done:
...
Furthermore, the developing-multiple-MFEs-at-once problem is just as much of an issue for edX.org devs as it is for Open edX community devs, so solving that is a win for everyone.
Prior Art
TODO: Flesh this out
Regis’ Open edX Micromanager: http://github.com/overhangio/openedx-micromanager
Work-in-progress frontend-dist tool for edX MFEs that I started: https://github.com/kdmccormick/frontend-dist
David Joy’s code: ???
...