docs(learn): Migrate the legacy guide "Easy profiling for Node.js Applications" to the learn section

i18n/locales/en.json

@@ -40,7 +40,8 @@
             "nodejsTheDifferenceBetweenDevelopmentAndProduction": "Node.js, the difference between development and production",
             "nodejsWithTypescript": "Node.js with TypeScript",
             "nodejsWithWebassembly": "Node.js with WebAssembly",
-            "debugging": "Debugging Node.js"
+            "debugging": "Debugging Node.js",
+            "profiling": "Profiling Node.js Applications"
           }
         },
         "asynchronousWork": {

navigation.json

@@ -124,6 +124,10 @@
             "debugging": {
               "link": "/learn/getting-started/debugging",
               "label": "components.navigation.learn.gettingStarted.links.debugging"
+            },
+            "profiling": {
+              "link": "/learn/getting-started/profiling",
+              "label": "components.navigation.learn.gettingStarted.links.profiling"
             }
           }
         },

pages/en/guides/diagnostics/poor-performance/index.md

@@ -0,0 +1,36 @@
+---
+title: Poor Performance - Diagnostics
+layout: docs.hbs
+---
+
+# Poor Performance
+
+In this document you can learn about how to profile a Node.js process.
+
+- [Poor Performance](#poor-performance)
+  - [My application has a poor performance](#my-application-has-a-poor-performance)
+    - [Symptoms](#symptoms)
+    - [Debugging](#debugging)
+
+## My application has a poor performance
+
+### Symptoms
+
+My applications latency is high and I have already confirmed that the bottleneck
+is not my dependencies like databases and downstream services. So I suspect that
+my application spends significant time to run code or process information.
+
+You are satisfied with your application performance in general but would like to
+understand which part of our application can be improved to run faster or more
+efficient. It can be useful when we want to improve the user experience or save
+computation cost.
+
+### Debugging
+
+In this use-case, we are interested in code pieces that use more CPU cycles than
+the others. When we do this locally, we usually try to optimize our code.
+
+This document provides two simple ways to profile a Node.js application:
+
+- [Using V8 Sampling Profiler](/learn/getting-started/profiling/)
+- [Using Linux Perf](/learn/diagnostics/poor-performance/using-linux-perf)

pages/en/guides/index.md

@@ -9,7 +9,7 @@ layout: docs.hbs
 
 ## General
 
-- [Easy profiling for Node.js Applications](/guides/simple-profiling/)
+- [Diagnostics - User Journey](/guides/diagnostics/)
 - [Security Best Practices](/guides/security/)
 
 ## Node.js core concepts

pages/en/learn/diagnostics/poor-performance/index.md

@@ -27,5 +27,5 @@ the others. When we do this locally, we usually try to optimize our code.
 
 This document provides two simple ways to profile a Node.js application:
 
-- [Using V8 Sampling Profiler](/guides/simple-profiling/)
+- [Using V8 Sampling Profiler](/learn/getting-started/profiling/)
 - [Using Linux Perf](/learn/diagnostics/poor-performance/using-linux-perf)

pages/en/guides/simple-profiling.md → pages/en/learn/getting-started/profiling.md

@@ -1,9 +1,9 @@
 ---
-title: Easy profiling for Node.js Applications
-layout: docs.hbs
+title: Profiling Node.js Applications
+layout: learn.hbs
 ---
 
-# Easy profiling for Node.js Applications
+# Profiling Node.js Applications
 
 There are many third party tools available for profiling Node.js applications
 but, in many cases, the easiest option is to use the Node.js built-in profiler.

redirects.json

@@ -180,6 +180,10 @@
       "source": "/:locale/docs/guides/timers-in-node/",
       "destination": "/:locale/learn/asynchronous-work/discover-javascript-timers"
     },
+    {
+      "source": "/:locale/docs/guides/simple-profiling",
+      "destination": "/:locale/learn/getting-started/profiling"
+    },
     {
       "source": "/:locale/docs/es6",
       "destination": "/:locale/learn/getting-started/ecmascript-2015-es6-and-beyond"