feat(docs): Adding videos for Node tutorials (#4007)

docs/node/tutorial/01-create-application.md

@@ -1,5 +1,9 @@
 # Step 1: Create Application
 
+## Video of this Lesson
+
+<iframe width="560" height="600" src="https://www.youtube.com/embed/UcBSBQYNlhE" frameborder="0" allow="accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
+
 In this tutorial you will use Nx to build a server application out of common libraries using modern technologies.
 
 ## Create a New Workspace

docs/node/tutorial/02-display-todos.md

@@ -1,5 +1,9 @@
 # Step 2: Display todos
 
+## Video of this Lesson
+
+<iframe width="560" height="600" src="https://www.youtube.com/embed/I4-sO2LeVbU" frameborder="0" allow="accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
+
 Great! We now have a server application set up to show some data when going to the `/api` route.
 
 Next, we're going to add a new service, and set up some server side templates.

docs/node/tutorial/03-share-code.md

@@ -1,5 +1,9 @@
 # Step 3: Share Code
 
+## Video of this Lesson
+
+<iframe width="560" height="600" src="https://www.youtube.com/embed/MqqwOoKa-Ho" frameborder="0" allow="accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
+
 Awesome! The application is working as expected!
 
 Next, let's work on refactoring a bit. What we're planning to do is move the `Todo` type to it's own library. This is important if we want to share the type between multiple applications, without having to duplicate the same type everywhere.

docs/node/tutorial/04-create-libs.md

@@ -1,5 +1,9 @@
 # Step 4: Create Libraries
 
+## Video of this Lesson
+
+<iframe width="560" height="600" src="https://www.youtube.com/embed/V29I_DHGlB8" frameborder="0" allow="accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
+
 Libraries are not just a way to share code in Nx. They are also useful for factoring out code into small units with a well-defined public API.
 
 ## Public API

docs/node/tutorial/05-dep-graph.md

@@ -1,5 +1,9 @@
 # Step 5: Dep Graph
 
+## Video of this Lesson
+
+<iframe width="560" height="600" src="https://www.youtube.com/embed/l9MjZ9IPdu4" frameborder="0" allow="accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
+
 An Nx workspace can contain dozens or hundreds of applications and libraries. As a codebase grows, it can be difficult to understand how they depend on each other and the implications of making a particular change.
 
 Previously, some senior architect would create an ad-hoc dependency diagram and upload it to a corporate wiki. The diagram is not correct even on Day 1 and gets more and more out of sync with every passing day.

docs/node/tutorial/06-computation-caching.md

@@ -1,5 +1,9 @@
 # Step 6: Computation Caching
 
+## Video of this Lesson
+
+<iframe width="560" height="600" src="https://www.youtube.com/embed/gXChzhI1Qpg" frameborder="0" allow="accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
+
 Nx has built-in computation caching, which drastically improves the performance of the commands.
 
 **To see it in action, run `nx build todos`:**

docs/node/tutorial/07-test-affected-projects.md

@@ -1,5 +1,9 @@
 # Step 7: Test Affected Projects
 
+## Video of this Lesson
+
+<iframe width="560" height="600" src="https://www.youtube.com/embed/TRRVLyHfN60" frameborder="0" allow="accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
+
 In addition to supporting computation caching, Nx can scale your development by doing code change analysis to see what apps or libraries are affected by a particular pull request.
 
 **Commit all the changes in the repo**: