neuland/micro-frontends

★ 4,675JavaScriptAudience · developerComplexity · 1/5LicenseSetup · easy

Mindmap

mindmap
  root((Micro-frontends))
    Core Concept
      Split UI into pieces
      Independent deployment
      Team ownership
    Relation to Backend
      Like microservices
      Frontend equivalent
    Content Location
      micro-frontends.org
      GitHub Pages hosted
    Contributing
      Open issues
      Submit pull requests

mindmap root((Micro-frontends)) Core Concept Split UI into pieces Independent deployment Team ownership Relation to Backend Like microservices Frontend equivalent Content Location micro-frontends.org GitHub Pages hosted Contributing Open issues Submit pull requests

Click or tap to explore — scroll the page freely

Things people build with this

USE CASE 1

Learn what micro-frontends are and how to apply the concept to your web application architecture.

USE CASE 2

Contribute edits or new content to the micro-frontends.org reference site via pull requests.

USE CASE 3

Share this site with teammates or stakeholders as an educational resource on UI architecture patterns.

USE CASE 4

Use as a reference for explaining micro-frontend architecture when proposing it to your team.

Tech stack

JavaScriptGitHub PagesMarkdown

Getting it running

Difficulty · easy Time to first run · 5min

Use freely for any purpose, including commercial, as long as you keep the copyright notice.

In plain English

This repository holds the source for micro-frontends.org, a website about applying microservice thinking to the front-end layer of web development. The idea of micro-frontends is to break a web application's user interface into independently owned and deployable pieces, the same way backend microservice architectures split server-side systems into separate services. The actual explanatory content and articles live on the website rather than in this repository's code. The README itself is minimal. It names the author, Michael Geers, links to the live site at micro-frontends.org, and explains that the site is hosted via GitHub Pages using an index.md file in the repository. There are no code examples, setup guides, architecture diagrams, or technical walkthroughs in the README. If you are looking for a practical explanation of what micro-frontends are and how to implement them, the README simply points you to the website rather than providing that information directly. Contributions to the site are welcome. Because the site is served directly from this repository via GitHub Pages, you can open issues or submit pull requests against the source files to suggest edits or additions to the published content. The project is licensed under the MIT License, attributed to neuland Buro fur Informatik, a software firm based in Bremen, Germany. The MIT License allows anyone to freely use, copy, modify, and distribute the material, including for commercial purposes, as long as the original copyright notice is preserved. This is a content and website repository, not a software library or an installable framework you can add to a project.

Copy-paste prompts

Prompt 1

Using the micro-frontends approach described on micro-frontends.org, help me plan how to split my e-commerce site's cart and product pages into independently deployable UI modules.

Prompt 2

How can I contribute a new article or correction to micro-frontends.org by submitting a pull request to the neuland/micro-frontends repo?

Prompt 3

Write a short explanation of micro-frontends that I can share with my non-technical manager, based on the concepts from micro-frontends.org.

Prompt 4

Help me evaluate whether my React monolith should be refactored into micro-frontends, using the criteria from the micro-frontends.org guide.

Prompt 5

What are the main trade-offs of adopting micro-frontends for a small team versus a large organization, based on the micro-frontends.org content?

Open on GitHub → Explain another repo

← neuland on gitmyhub — every repo by this author, as a profile.

Verify against the repo before relying on details.