# microfrontends.dev > An interactive, source-backed guide to whether your team needs micro frontends, and if so, which approach fits. Every page below links its Markdown version. Each page states its sources; opinions and ratings are labelled as editorial judgement. The full text of every page in one file: https://microfrontends.dev/llms-full.txt ## Fundamentals - [Fundamentals](https://microfrontends.dev/learn.md): Short, layered lessons on what micro frontends are, the problems they solve, and when not to use them. - [What are micro frontends](https://microfrontends.dev/learn/what-are-micro-frontends.md): Micro frontends in plain words: independently delivered frontend pieces that teams own and that are composed into one experience. - [Problems they solve](https://microfrontends.dev/learn/problems-they-solve.md): Why teams adopt micro frontends (team autonomy, independent deploys, smaller codebases, step-by-step migration) and the problems they don't solve. - [When NOT to use them](https://microfrontends.dev/learn/when-not-to-use.md): The costs of micro frontends (complexity, payload, consistency, tooling) and why many teams are better served by a well-structured monolith. ## Approaches - [Approaches](https://microfrontends.dev/approaches.md): Every way to put a micro frontend together, each with the same template and ratings. - [Build-time packages](https://microfrontends.dev/approaches/build-time-packages.md): Build-time micro frontends: each team publishes its part as a versioned npm package, and the shell installs them and ships one bundle. - [Module Federation](https://microfrontends.dev/approaches/module-federation.md): Module Federation for micro frontends: each team builds and deploys its own bundle, and the shell loads them at runtime and shares common dependencies. - [Native Federation / import maps](https://microfrontends.dev/approaches/native-federation-import-maps.md): Micro frontends on browser-native ES modules and import maps: Module Federation's remotes and shared dependencies without one bundler's runtime. - [single-spa](https://microfrontends.dev/approaches/single-spa.md): single-spa for micro frontends: a root config registers each app with the routes it owns, then mounts and unmounts them, whatever their framework. - [Web Components](https://microfrontends.dev/approaches/web-components.md): Web Components for micro frontends: each team ships custom elements any page or framework can use, with Shadow DOM available to keep styles apart. - [iframes](https://microfrontends.dev/approaches/iframes.md): iframes for micro frontends: each team's app is a separate page shown in a frame, with the strongest isolation and the highest cost. - [Server and edge composition](https://microfrontends.dev/approaches/server-and-edge-composition.md): Server and edge composition for micro frontends: team-owned HTML fragments are assembled on the server or at the CDN edge, so the browser gets one page. - [Modular monolith and monorepo](https://microfrontends.dev/approaches/alternatives.md): Often the better alternative to micro frontends: one app and one deploy, split into team-owned modules whose boundaries are enforced by tooling. ## Tools - [Compare approaches](https://microfrontends.dev/compare.md): Every approach rated 1–5 on the same criteria, with the reason behind each rating. - [Decision check](https://microfrontends.dev/decide.md): Ten questions about your teams and constraints, ending in a transparent recommendation. - [How the decision check works](https://microfrontends.dev/decide/how-it-works.md): The complete logic: every question, readiness point, penalty, band, rule and approach weight. ## Reference - [Glossary](https://microfrontends.dev/glossary.md): Every micro frontend term in one sentence, with a longer explanation and where it is taught. - [Sources & method](https://microfrontends.dev/sources.md): Every source the site cites, with the pages that rely on each one. ## Project - [Home](https://microfrontends.dev/index.md): An interactive guide to micro frontends: what they are, whether your team needs them, and which approach fits. - [About](https://microfrontends.dev/about.md): Why the site exists, how ratings and the decision check work, how content is reviewed, and how to contribute. - [Privacy](https://microfrontends.dev/privacy.md): What the site does and does not do with your data, and what a share link contains.