Hi,
I read from Release v22.0.0 · overhangio/tutor-mfe · GitHub that frontend-base based MFE are not enabled by default for authn and learner-dashboard. I usually look forward to avoid double development by developing/testing my platform for the future. Is there any reason I should not enable those ?
The reason they’re not enabled by default is just to minimize the surprise factor for operators that are upgrading to Verawood. The new apps look and work the same out of the box, but under the hood they’re significantly different. For instance, if an operator enables them, it’s likely they’ll have to adapt any existing customization (such as plugins or branding) to work properly with them.
See the howto we wrote on converting plugins into frontend-base apps, for example. Or the theming howto in frontend-base itself. And finally, the compat layer we’re hoping will be useful in some cases (it’s supported by tutor-mfe.)
This is exactly why we tried to make it as easy as possible to enable the new apps, even though they’re not enabled by default. If you have the resources to do so, I strongly recommend you do enable the apps now and get ahead on anything you’ll eventually have to tackle anyway.
(We’re targetting Willow to have all learner-facing MFEs converted to frontend-base apps and enabled by default. All the rest by Xylon. With any luck, by the Y release - December 2027 - the legacy MFEs will be gone. You can track progress using this board.)
Thanks. I see.
Sadly, this means that in order to have a coherent UI, we now need 3 sets of theming: one for legacy pages, one for MFEs, and one for frontend-base apps. Hopefully this is the last set of theming changes.
We’re keenly aware of this problem. As I mentioned earlier, the frontend-base conversion aims to be done for the Xylon release. And so is the conversion of legacy pages, which you can track using this epic.
The answer to the top post is also in the Verawood release notes, which were just published.