diff --git a/radar/2018-03-01/micro-frontends.md b/radar/2018-03-01/micro-frontends.md
index e062be8..112b808 100644
--- a/radar/2018-03-01/micro-frontends.md
+++ b/radar/2018-03-01/micro-frontends.md
@@ -12,6 +12,6 @@ challenges. Integrating different Frontends on the client- or server-side can be
 User Experience consistent.
 
 Despite the challenges, Micro Frontends help us to develop large applications across multiple teams. Developers can
-work more independently without having too much trouble maintaining a large codebase. Being able to update oder 
+work more independently without having too much trouble maintaining a large codebase. Being able to update or 
 replace Frontend libraries in some parts of the application is yet another benefit in the fast-moving world of 
 frontend development.
diff --git a/radar/2021-01-01/micro-frontends.md b/radar/2021-01-01/micro-frontends.md
new file mode 100644
index 0000000..914032b
--- /dev/null
+++ b/radar/2021-01-01/micro-frontends.md
@@ -0,0 +1,9 @@
+---
+title:      "Micro Frontends"
+ring:       adopt
+quadrant:   methods-and-patterns
+---
+
+The Micro Frontends approach continues to prove to be a valuable pattern for large-scale systems developed by several teams. Therefore, we moved this pattern to "adopt".
+
+We use [page composing](methods-and-patterns/page-composing.html) as one implementation of this pattern.
\ No newline at end of file
diff --git a/radar/2021-01-01/page-composing.md b/radar/2021-01-01/page-composing.md
new file mode 100644
index 0000000..4a3a614
--- /dev/null
+++ b/radar/2021-01-01/page-composing.md
@@ -0,0 +1,13 @@
+---
+title:      "Page Composing"
+ring:       trial
+quadrant:   methods-and-patterns
+---
+
+Page composing is a way to aggregate multiple independent page fragments into one combined web page. As an implementation of [Micro Frontends](methods-and-patterns/micro-frontends.html), this approach supports to deploy and run services agnostic to the technologies used per team.
+
+The concept builds upon the fact that all involved services deliver valid HTML as their output. Our solution is a small application which takes care of gathering the page fragments from all services and composing each into a defined HTML template. A configuration layer further allows to control which fragment gets pulled from the serving instance.
+
+With such a page composing application in place, teams can autonomously develop, deploy and operate their service with the freedom of choosing technologies and release strategies.
+
+Martin Fowler et al. described this as [Server-side template composition](https://martinfowler.com/articles/micro-frontends.html#Server-sideTemplateComposition).
\ No newline at end of file