The Micro Front End approach has been very successful in a lot of ways. I am a fan of the project. However, it’s very slow to use on the authoring side, partly because it involves two page loads every time you edit a component. I know one of the goals was to make it faster to author content, but the combination of the page loads and the visual editor has actually slowed us down. I’d love to see it sped back up.
I don’t know what it would take to actually do that, but I’m happy to provide input / feedback / brainstorming if it would be helpful.
This is a hugely important topic, and would benefit from broader brainstorming - so much so that this may be a good working group / meeting topic more broadly to identify which specific steps of authoring components are contributing to authoring slow downs.
I could imagine this also being a useful Design working group workshop topic, I can flag this as a potential topic for the future and perhaps we find a time that educators can attend in the coming months to do this. FYI @edSchema , @sdaitzman , @ali_hugo
Two example editing speed areas to explore below
Inline / Embedded Component Editing
One of the recent changes that I think was made regarding component editing is to load the component editors as a modal instead of a separate URL from the unit pages, working toward being able to get it back embedded on the page directly as it once was pre-MFEs. I forget whether this was in the last named release or will be in Ulmo…
Reduce Component Creation Clicks for Advanced Problem Workflows
Separately, I know that some authoring workflows that rely on advanced editors / OLX / Markdown have several steps / clicks for problem authoring. Providing ways to surface templates for problems (and other blocks) more quickly is something we are looking into as part of the continuation work on the “Visually Configure Course Blocks” projects but this also merits probably its own proposal / document for input and review.