From 2b0ca51ca0cb45387133c5bc13d35f3feef498f9 Mon Sep 17 00:00:00 2001
From: Gabriel Grubba <70247653+Grubba27@users.noreply.github.com>
Date: Tue, 12 Mar 2024 10:59:55 -0300
Subject: [PATCH] add migration guide for blaze

---
 v3-docs/v3-migration-docs/front-end/blaze.md | 16 ++++++++++++++++
 1 file changed, 16 insertions(+)

diff --git a/v3-docs/v3-migration-docs/front-end/blaze.md b/v3-docs/v3-migration-docs/front-end/blaze.md
index 571da502ef..fbdfaaf447 100644
--- a/v3-docs/v3-migration-docs/front-end/blaze.md
+++ b/v3-docs/v3-migration-docs/front-end/blaze.md
@@ -1 +1,17 @@
 # Blaze changes
+
+
+It is important to note that migrating your front-end code to async is unnecessary.
+You can still use the sync methods on the client side.
+
+But to maintain isomorphic code, you can use the async methods on the client side.
+
+Since this [PR](https://github.com/meteor/blaze/pull/413) was released with Blaze 2.7. Blaze supports async in their views.
+
+You can check the [Blaze docs](https://www.blazejs.org/api/spacebars#Async-states) for
+more information on how to handle async states.
+
+[@radekmie](https://github.com/radekmie) made two great posts about making Blaze async. Both are worth reading:
+  - [On Asynchronicity in Blaze](https://radekmie.dev/blog/on-asynchronicity-in-blaze/);
+  - [On Asynchronicity in Blaze (again)](https://radekmie.dev/blog/on-asynchronicity-in-blaze-again/);
+