Overview
How the Microfrontends page of the MFE Orchestrator console lists, groups and gives you access to every microfrontend registered in a project.
Create a microfrontend
Add a microfrontend from a template, which scaffolds a repository and a build pipeline for you, or by registering code that already exists elsewhere.
Hosting options
Every microfrontend declares where its files live: the MFE Orchestrator hub, a storage bucket you own, or a URL you already serve. What each option changes.
Versions and builds
How a microfrontend version comes into existence, what a version string means to the platform, and the two ways to produce and upload build artifacts.
Hosts and remotes
How MFE Orchestrator models the parent and child relationships between hosts and remotes, and how it turns that graph into Module Federation configuration.
Canary releases
Serve a new version of a microfrontend to a fraction of your traffic while everyone else keeps the stable one, with a sticky decision taken entirely server-side.