Backbase
diff --git a/‎content/posts/unpublished/maintaining-legacy-code-with-micro-frontends/assets/banner.png renamed to ‎content/posts/2024/05/15/maintaining-legacy-code-with-micro-frontends/assets/banner.png b/‎content/posts/unpublished/maintaining-legacy-code-with-micro-frontends/assets/banner.png renamed to ‎content/posts/2024/05/15/maintaining-legacy-code-with-micro-frontends/assets/banner.png
diff --git a/‎content/posts/unpublished/maintaining-legacy-code-with-micro-frontends/assets/legacy-as-remote-journeys.jpg renamed to ‎content/posts/2024/05/15/maintaining-legacy-code-with-micro-frontends/assets/legacy-as-remote-journeys.jpg b/‎content/posts/unpublished/maintaining-legacy-code-with-micro-frontends/assets/legacy-as-remote-journeys.jpg renamed to ‎content/posts/2024/05/15/maintaining-legacy-code-with-micro-frontends/assets/legacy-as-remote-journeys.jpg
diff --git a/‎content/posts/unpublished/maintaining-legacy-code-with-micro-frontends/assets/legacy-as-remote-widgets.jpg renamed to ‎content/posts/2024/05/15/maintaining-legacy-code-with-micro-frontends/assets/legacy-as-remote-widgets.jpg b/‎content/posts/unpublished/maintaining-legacy-code-with-micro-frontends/assets/legacy-as-remote-widgets.jpg renamed to ‎content/posts/2024/05/15/maintaining-legacy-code-with-micro-frontends/assets/legacy-as-remote-widgets.jpg
diff --git a/‎content/posts/unpublished/maintaining-legacy-code-with-micro-frontends/assets/legacy-as-shell-journeys.jpg renamed to ‎content/posts/2024/05/15/maintaining-legacy-code-with-micro-frontends/assets/legacy-as-shell-journeys.jpg b/‎content/posts/unpublished/maintaining-legacy-code-with-micro-frontends/assets/legacy-as-shell-journeys.jpg renamed to ‎content/posts/2024/05/15/maintaining-legacy-code-with-micro-frontends/assets/legacy-as-shell-journeys.jpg
diff --git a/‎content/posts/unpublished/maintaining-legacy-code-with-micro-frontends/assets/legacy-as-shell-widgets.jpg renamed to ‎content/posts/2024/05/15/maintaining-legacy-code-with-micro-frontends/assets/legacy-as-shell-widgets.jpg b/‎content/posts/unpublished/maintaining-legacy-code-with-micro-frontends/assets/legacy-as-shell-widgets.jpg renamed to ‎content/posts/2024/05/15/maintaining-legacy-code-with-micro-frontends/assets/legacy-as-shell-widgets.jpg
diff --git a/‎content/posts/unpublished/maintaining-legacy-code-with-micro-frontends/post.md renamed to ‎content/posts/2024/05/15/maintaining-legacy-code-with-micro-frontends/post.md
Lines changed: 1 addition & 1 deletion b/‎content/posts/unpublished/maintaining-legacy-code-with-micro-frontends/post.md renamed to ‎content/posts/2024/05/15/maintaining-legacy-code-with-micro-frontends/post.md
Lines changed: 1 addition & 1 deletion
@@ -5,7 +5,7 @@ Taking advantage of Micro Frontends with Module Federation to maintain legacy ap
 ![](assets/banner.png)
 
 Authors: Pablo Villoslada Puigcerber
-Date: unpublished
+Date: 2024-05-15T13:51:39.651Z
 Category: frontend
 
 tags: angular,frontend,micro-frontends,module-federation,web