From 51f8437a1694bc96d59ed2588efea26ea157c04c Mon Sep 17 00:00:00 2001 From: Zachary DeRose Date: Thu, 5 Nov 2020 07:01:00 -0700 Subject: [PATCH] feat(docs): Adding videos for Node tutorials (#4007) --- docs/node/tutorial/01-create-application.md | 4 ++++ docs/node/tutorial/02-display-todos.md | 4 ++++ docs/node/tutorial/03-share-code.md | 4 ++++ docs/node/tutorial/04-create-libs.md | 4 ++++ docs/node/tutorial/05-dep-graph.md | 4 ++++ docs/node/tutorial/06-computation-caching.md | 4 ++++ docs/node/tutorial/07-test-affected-projects.md | 4 ++++ 7 files changed, 28 insertions(+) diff --git a/docs/node/tutorial/01-create-application.md b/docs/node/tutorial/01-create-application.md index c4a30f5e02..619991a46d 100644 --- a/docs/node/tutorial/01-create-application.md +++ b/docs/node/tutorial/01-create-application.md @@ -1,5 +1,9 @@ # Step 1: Create Application +## Video of this Lesson + + + In this tutorial you will use Nx to build a server application out of common libraries using modern technologies. ## Create a New Workspace diff --git a/docs/node/tutorial/02-display-todos.md b/docs/node/tutorial/02-display-todos.md index 17f96d7c8e..3b145b56c6 100644 --- a/docs/node/tutorial/02-display-todos.md +++ b/docs/node/tutorial/02-display-todos.md @@ -1,5 +1,9 @@ # Step 2: Display todos +## Video of this Lesson + + + 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. diff --git a/docs/node/tutorial/03-share-code.md b/docs/node/tutorial/03-share-code.md index 7b38e03eed..2cc3410e83 100644 --- a/docs/node/tutorial/03-share-code.md +++ b/docs/node/tutorial/03-share-code.md @@ -1,5 +1,9 @@ # Step 3: Share Code +## Video of this Lesson + + + 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. diff --git a/docs/node/tutorial/04-create-libs.md b/docs/node/tutorial/04-create-libs.md index 673c32ad26..8e341993a9 100644 --- a/docs/node/tutorial/04-create-libs.md +++ b/docs/node/tutorial/04-create-libs.md @@ -1,5 +1,9 @@ # Step 4: Create Libraries +## Video of this Lesson + + + 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 diff --git a/docs/node/tutorial/05-dep-graph.md b/docs/node/tutorial/05-dep-graph.md index b2de816aae..3047bedf2d 100644 --- a/docs/node/tutorial/05-dep-graph.md +++ b/docs/node/tutorial/05-dep-graph.md @@ -1,5 +1,9 @@ # Step 5: Dep Graph +## Video of this Lesson + + + 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. diff --git a/docs/node/tutorial/06-computation-caching.md b/docs/node/tutorial/06-computation-caching.md index 592cee95d2..52431ba203 100644 --- a/docs/node/tutorial/06-computation-caching.md +++ b/docs/node/tutorial/06-computation-caching.md @@ -1,5 +1,9 @@ # Step 6: Computation Caching +## Video of this Lesson + + + Nx has built-in computation caching, which drastically improves the performance of the commands. **To see it in action, run `nx build todos`:** diff --git a/docs/node/tutorial/07-test-affected-projects.md b/docs/node/tutorial/07-test-affected-projects.md index ac17c9c90d..15833a3df8 100644 --- a/docs/node/tutorial/07-test-affected-projects.md +++ b/docs/node/tutorial/07-test-affected-projects.md @@ -1,5 +1,9 @@ # Step 7: Test Affected Projects +## Video of this Lesson + + + 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**: