diff --git a/components/SideNavigation.tsx b/components/SideNavigation.tsx
index 7aa43aadf0668..e17549fc77c8d 100644
--- a/components/SideNavigation.tsx
+++ b/components/SideNavigation.tsx
@@ -21,15 +21,25 @@ const SideNavigation: FC<SideNavigationProps> = ({
 
   const sideNavigationItems = getSideNavigation(navigationKey, context);
 
-  const getLinkClassName = (href: string) =>
-    classNames({ active: isCurrentLocaleRoute(href) });
+  const getLinkClasses = (href: string, level: number) =>
+    classNames({ active: isCurrentLocaleRoute(href), level });
 
   return (
     <nav aria-label="secondary">
       <ul>
-        {sideNavigationItems.map((item, key) => (
-          <li key={key} className={getLinkClassName(item.link)}>
+        {sideNavigationItems.map(item => (
+          <li key={item.key} className={getLinkClasses(item.link, item.level)}>
             <LocalizedLink href={item.link}>{item.text}</LocalizedLink>
+
+            {item.items.length > 0 && (
+              <ul>
+                {item.items.map(({ link, level, text, key }) => (
+                  <li key={key} className={getLinkClasses(link, level)}>
+                    <LocalizedLink href={link}>{text}</LocalizedLink>
+                  </li>
+                ))}
+              </ul>
+            )}
           </li>
         ))}
       </ul>
diff --git a/crowdin.yml b/crowdin.yml
index 05ee4566e2cb4..a5018ad750d6e 100644
--- a/crowdin.yml
+++ b/crowdin.yml
@@ -8,6 +8,7 @@ files:
     content_segmentation: 0
     ignore:
       - /pages/en/blog/**/*.md
+      - /pages/en/learn/**/*.md
       - /pages/en/docs/guides/**/*.md
       - /pages/en/download/index.md
       - /pages/en/download/current.md
@@ -22,6 +23,7 @@ files:
     content_segmentation: 0
     ignore:
       - /pages/en/blog/**/*.mdx
+      - /pages/en/learn/**/*.mdx
       - /pages/en/docs/guides/**/*.mdx
     languages_mapping:
       two_letters_code:
diff --git a/hooks/useNavigation.tsx b/hooks/useNavigation.tsx
index fc28aa611d653..acba55f2ce64a 100644
--- a/hooks/useNavigation.tsx
+++ b/hooks/useNavigation.tsx
@@ -6,6 +6,15 @@ import type { NavigationEntry, NavigationKeys } from '@/types';
 // Translation Context for FormattedMessage
 type Context = Record<string, Record<string, string | JSX.Element | undefined>>;
 
+// These are mapped navigation entries. Navigation Entries can have sub-entries
+type MappedItems = {
+  text: JSX.Element;
+  link: string;
+  key: string;
+  level: number;
+  items: MappedItems[];
+};
+
 // Provides Context replacement for variables within the Link. This is also something that is not going
 // to happen in the future with `nodejs/nodejs.dev` codebase
 const replaceLinkWithContext = (
@@ -24,8 +33,9 @@ const replaceLinkWithContext = (
 export const useNavigation = () => {
   const mapNavigationEntries = (
     entries: Record<string, NavigationEntry>,
-    context?: Context
-  ) => {
+    context?: Context,
+    level = 0
+  ): MappedItems[] => {
     const getContext = (key: string) => (context && context[key]) || {};
 
     const getFormattedMessage = (translationId: string, key: string) => (
@@ -35,20 +45,23 @@ export const useNavigation = () => {
     return Object.entries(entries).map(([key, item]) => ({
       text: getFormattedMessage(item.translationId, key),
       link: replaceLinkWithContext(item.link, getContext(key)),
+      items: item.items
+        ? mapNavigationEntries(item.items, context, level + 1)
+        : [],
+      level,
       key: key,
     }));
   };
 
   return {
     navigationItems: mapNavigationEntries(siteNavigation),
-    getSideNavigation: (section: NavigationKeys, context?: Context) =>
-      mapNavigationEntries(
-        // We need the parent and their items when making a side navigation
-        {
-          [section]: siteNavigation[section],
-          ...siteNavigation[section].items,
-        },
+    getSideNavigation: (section: NavigationKeys, context?: Context) => {
+      const { items, translationId, link } = siteNavigation[section];
+
+      return mapNavigationEntries(
+        { [section]: { translationId, link }, ...items },
         context
-      ),
+      );
+    },
   };
 };
diff --git a/i18n/locales/ar.json b/i18n/locales/ar.json
index bf5ff792c29c0..c421b79c69435 100644
--- a/i18n/locales/ar.json
+++ b/i18n/locales/ar.json
@@ -18,7 +18,7 @@
   "components.navigation.docs.links.es6": "ES6 and beyond",
   "components.navigation.docs.links.apiLts": "{fullLtsNodeVersion} API {spanLts}",
   "components.navigation.docs.links.apiCurrent": "{fullCurrentNodeVersion} API",
-  "components.navigation.docs.links.guides": "Guides",
+  "components.navigation.docs.links.guides": "Guides {spanGuides}",
   "components.navigation.docs.links.dependencies": "Dependencies",
   "components.navigation.getInvolved.links.collabSummit": "Collab Summit",
   "components.navigation.getInvolved.links.contribute": "Contribute",
@@ -69,9 +69,42 @@
   "components.common.card.announcement": "Announcements",
   "components.common.card.release": "Releases",
   "components.common.card.vulnerability": "Vulnerabilities",
-  "components.home.homeDownloadButton.download": "Download {version} {isLts, select, true {lts} other {current}}",
+  "components.home.homeDownloadButton.download": "{version} {isLts, select, true {LTS} other {Current}}",
   "components.home.homeDownloadButton.tagline": "{isLts, select, true {Recommended For Most Users} other {Latest Features}}",
   "components.home.homeDownloadButton.changelog": "Changelog",
   "components.home.homeDownloadButton.otherDownloads": "Other Downloads",
-  "components.home.homeDownloadButton.apiDocs": "API Docs"
+  "components.home.homeDownloadButton.apiDocs": "API Docs",
+  "components.header.links.learn": "Learn",
+  "components.header.links.learn.gettingStarted": "Getting Started",
+  "components.header.links.learn.gettingStarted.introductionToNodejs": "Introduction to Node.js",
+  "components.header.links.learn.gettingStarted.howToInstallNodejs": "How to install Node.js",
+  "components.header.links.learn.gettingStarted.howMuchJavascriptDoYouNeedToKnowToUseNodejs": "How much JavaScript do you need to know to use Node.js?",
+  "components.header.links.learn.gettingStarted.differencesBetweenNodejsAndTheBrowser": "Differences between Node.js and the Browser",
+  "components.header.links.learn.gettingStarted.theV8JavascriptEngine": "The V8 JavaScript Engine",
+  "components.header.links.learn.gettingStarted.anIntroductionToTheNpmPackageManager": "An introduction to the NPM package manager",
+  "components.header.links.learn.gettingStarted.ecmascript2015Es6AndBeyond": "ECMAScript 2015 (ES6) and beyond",
+  "components.header.links.learn.gettingStarted.nodejsTheDifferenceBetweenDevelopmentAndProduction": "Node.js, the difference between development and production",
+  "components.header.links.learn.gettingStarted.nodejsWithTypescript": "Node.js with TypeScript",
+  "components.header.links.learn.gettingStarted.nodejsWithWebassembly": "Node.js with WebAssembly",
+  "components.header.links.learn.asynchronousWork": "Asynchronous Work",
+  "components.header.links.learn.asynchronousWork.asynchronousFlowControl": "Asynchronous flow control",
+  "components.header.links.learn.asynchronousWork.overviewOfBlockingVsNonBlocking": "Overview of Blocking vs Non-Blocking",
+  "components.header.links.learn.asynchronousWork.javascriptAsynchronousProgrammingAndCallbacks": "JavaScript Asynchronous Programming and Callbacks",
+  "components.header.links.learn.asynchronousWork.discoverJavaScriptTimers": "Discover JavaScript Timers",
+  "components.header.links.learn.asynchronousWork.understandingProcessnexttick": "Understanding process.nextTick()",
+  "components.header.links.learn.asynchronousWork.understandingSetimmediate": "Understanding setImmediate()",
+  "components.header.links.learn.asynchronousWork.theNodejsEventEmitter": "The Node.js Event emitter",
+  "components.header.links.learn.manipulatingFiles": "Manipulating Files",
+  "components.header.links.learn.manipulatingFiles.nodejsFileStats": "Node.js file stats",
+  "components.header.links.learn.manipulatingFiles.nodejsFilePaths": "Node.js File Paths",
+  "components.header.links.learn.manipulatingFiles.workingWithFileDescriptorsInNodejs": "Working with file descriptors in Node.js",
+  "components.header.links.learn.manipulatingFiles.readingFilesWithNodejs": "Reading files with Node.js",
+  "components.header.links.learn.manipulatingFiles.writingFilesWithNodejs": "Writing files with Node.js",
+  "components.header.links.learn.manipulatingFiles.workingWithFoldersInNodejs": "Working with folders in Node.js",
+  "components.header.links.learn.commandLine": "Command Line",
+  "components.header.links.learn.commandLine.runNodejsScriptsFromTheCommandLine": "Run Node.js scripts from the command line",
+  "components.header.links.learn.commandLine.howToReadEnvironmentVariablesFromNodejs": "How to read environment variables from Node.js",
+  "components.header.links.learn.commandLine.howToUseTheNodejsRepl": "How to use the Node.js REPL",
+  "components.header.links.learn.commandLine.outputToTheCommandLineUsingNodejs": "Output to the command line using Node.js",
+  "components.header.links.learn.commandLine.acceptInputFromTheCommandLineInNodejs": "Accept input from the command line in Node.js"
 }
diff --git a/i18n/locales/de.json b/i18n/locales/de.json
index bf5ff792c29c0..c421b79c69435 100644
--- a/i18n/locales/de.json
+++ b/i18n/locales/de.json
@@ -18,7 +18,7 @@
   "components.navigation.docs.links.es6": "ES6 and beyond",
   "components.navigation.docs.links.apiLts": "{fullLtsNodeVersion} API {spanLts}",
   "components.navigation.docs.links.apiCurrent": "{fullCurrentNodeVersion} API",
-  "components.navigation.docs.links.guides": "Guides",
+  "components.navigation.docs.links.guides": "Guides {spanGuides}",
   "components.navigation.docs.links.dependencies": "Dependencies",
   "components.navigation.getInvolved.links.collabSummit": "Collab Summit",
   "components.navigation.getInvolved.links.contribute": "Contribute",
@@ -69,9 +69,42 @@
   "components.common.card.announcement": "Announcements",
   "components.common.card.release": "Releases",
   "components.common.card.vulnerability": "Vulnerabilities",
-  "components.home.homeDownloadButton.download": "Download {version} {isLts, select, true {lts} other {current}}",
+  "components.home.homeDownloadButton.download": "{version} {isLts, select, true {LTS} other {Current}}",
   "components.home.homeDownloadButton.tagline": "{isLts, select, true {Recommended For Most Users} other {Latest Features}}",
   "components.home.homeDownloadButton.changelog": "Changelog",
   "components.home.homeDownloadButton.otherDownloads": "Other Downloads",
-  "components.home.homeDownloadButton.apiDocs": "API Docs"
+  "components.home.homeDownloadButton.apiDocs": "API Docs",
+  "components.header.links.learn": "Learn",
+  "components.header.links.learn.gettingStarted": "Getting Started",
+  "components.header.links.learn.gettingStarted.introductionToNodejs": "Introduction to Node.js",
+  "components.header.links.learn.gettingStarted.howToInstallNodejs": "How to install Node.js",
+  "components.header.links.learn.gettingStarted.howMuchJavascriptDoYouNeedToKnowToUseNodejs": "How much JavaScript do you need to know to use Node.js?",
+  "components.header.links.learn.gettingStarted.differencesBetweenNodejsAndTheBrowser": "Differences between Node.js and the Browser",
+  "components.header.links.learn.gettingStarted.theV8JavascriptEngine": "The V8 JavaScript Engine",
+  "components.header.links.learn.gettingStarted.anIntroductionToTheNpmPackageManager": "An introduction to the NPM package manager",
+  "components.header.links.learn.gettingStarted.ecmascript2015Es6AndBeyond": "ECMAScript 2015 (ES6) and beyond",
+  "components.header.links.learn.gettingStarted.nodejsTheDifferenceBetweenDevelopmentAndProduction": "Node.js, the difference between development and production",
+  "components.header.links.learn.gettingStarted.nodejsWithTypescript": "Node.js with TypeScript",
+  "components.header.links.learn.gettingStarted.nodejsWithWebassembly": "Node.js with WebAssembly",
+  "components.header.links.learn.asynchronousWork": "Asynchronous Work",
+  "components.header.links.learn.asynchronousWork.asynchronousFlowControl": "Asynchronous flow control",
+  "components.header.links.learn.asynchronousWork.overviewOfBlockingVsNonBlocking": "Overview of Blocking vs Non-Blocking",
+  "components.header.links.learn.asynchronousWork.javascriptAsynchronousProgrammingAndCallbacks": "JavaScript Asynchronous Programming and Callbacks",
+  "components.header.links.learn.asynchronousWork.discoverJavaScriptTimers": "Discover JavaScript Timers",
+  "components.header.links.learn.asynchronousWork.understandingProcessnexttick": "Understanding process.nextTick()",
+  "components.header.links.learn.asynchronousWork.understandingSetimmediate": "Understanding setImmediate()",
+  "components.header.links.learn.asynchronousWork.theNodejsEventEmitter": "The Node.js Event emitter",
+  "components.header.links.learn.manipulatingFiles": "Manipulating Files",
+  "components.header.links.learn.manipulatingFiles.nodejsFileStats": "Node.js file stats",
+  "components.header.links.learn.manipulatingFiles.nodejsFilePaths": "Node.js File Paths",
+  "components.header.links.learn.manipulatingFiles.workingWithFileDescriptorsInNodejs": "Working with file descriptors in Node.js",
+  "components.header.links.learn.manipulatingFiles.readingFilesWithNodejs": "Reading files with Node.js",
+  "components.header.links.learn.manipulatingFiles.writingFilesWithNodejs": "Writing files with Node.js",
+  "components.header.links.learn.manipulatingFiles.workingWithFoldersInNodejs": "Working with folders in Node.js",
+  "components.header.links.learn.commandLine": "Command Line",
+  "components.header.links.learn.commandLine.runNodejsScriptsFromTheCommandLine": "Run Node.js scripts from the command line",
+  "components.header.links.learn.commandLine.howToReadEnvironmentVariablesFromNodejs": "How to read environment variables from Node.js",
+  "components.header.links.learn.commandLine.howToUseTheNodejsRepl": "How to use the Node.js REPL",
+  "components.header.links.learn.commandLine.outputToTheCommandLineUsingNodejs": "Output to the command line using Node.js",
+  "components.header.links.learn.commandLine.acceptInputFromTheCommandLineInNodejs": "Accept input from the command line in Node.js"
 }
diff --git a/i18n/locales/en.json b/i18n/locales/en.json
index bf5ff792c29c0..c421b79c69435 100644
--- a/i18n/locales/en.json
+++ b/i18n/locales/en.json
@@ -18,7 +18,7 @@
   "components.navigation.docs.links.es6": "ES6 and beyond",
   "components.navigation.docs.links.apiLts": "{fullLtsNodeVersion} API {spanLts}",
   "components.navigation.docs.links.apiCurrent": "{fullCurrentNodeVersion} API",
-  "components.navigation.docs.links.guides": "Guides",
+  "components.navigation.docs.links.guides": "Guides {spanGuides}",
   "components.navigation.docs.links.dependencies": "Dependencies",
   "components.navigation.getInvolved.links.collabSummit": "Collab Summit",
   "components.navigation.getInvolved.links.contribute": "Contribute",
@@ -69,9 +69,42 @@
   "components.common.card.announcement": "Announcements",
   "components.common.card.release": "Releases",
   "components.common.card.vulnerability": "Vulnerabilities",
-  "components.home.homeDownloadButton.download": "Download {version} {isLts, select, true {lts} other {current}}",
+  "components.home.homeDownloadButton.download": "{version} {isLts, select, true {LTS} other {Current}}",
   "components.home.homeDownloadButton.tagline": "{isLts, select, true {Recommended For Most Users} other {Latest Features}}",
   "components.home.homeDownloadButton.changelog": "Changelog",
   "components.home.homeDownloadButton.otherDownloads": "Other Downloads",
-  "components.home.homeDownloadButton.apiDocs": "API Docs"
+  "components.home.homeDownloadButton.apiDocs": "API Docs",
+  "components.header.links.learn": "Learn",
+  "components.header.links.learn.gettingStarted": "Getting Started",
+  "components.header.links.learn.gettingStarted.introductionToNodejs": "Introduction to Node.js",
+  "components.header.links.learn.gettingStarted.howToInstallNodejs": "How to install Node.js",
+  "components.header.links.learn.gettingStarted.howMuchJavascriptDoYouNeedToKnowToUseNodejs": "How much JavaScript do you need to know to use Node.js?",
+  "components.header.links.learn.gettingStarted.differencesBetweenNodejsAndTheBrowser": "Differences between Node.js and the Browser",
+  "components.header.links.learn.gettingStarted.theV8JavascriptEngine": "The V8 JavaScript Engine",
+  "components.header.links.learn.gettingStarted.anIntroductionToTheNpmPackageManager": "An introduction to the NPM package manager",
+  "components.header.links.learn.gettingStarted.ecmascript2015Es6AndBeyond": "ECMAScript 2015 (ES6) and beyond",
+  "components.header.links.learn.gettingStarted.nodejsTheDifferenceBetweenDevelopmentAndProduction": "Node.js, the difference between development and production",
+  "components.header.links.learn.gettingStarted.nodejsWithTypescript": "Node.js with TypeScript",
+  "components.header.links.learn.gettingStarted.nodejsWithWebassembly": "Node.js with WebAssembly",
+  "components.header.links.learn.asynchronousWork": "Asynchronous Work",
+  "components.header.links.learn.asynchronousWork.asynchronousFlowControl": "Asynchronous flow control",
+  "components.header.links.learn.asynchronousWork.overviewOfBlockingVsNonBlocking": "Overview of Blocking vs Non-Blocking",
+  "components.header.links.learn.asynchronousWork.javascriptAsynchronousProgrammingAndCallbacks": "JavaScript Asynchronous Programming and Callbacks",
+  "components.header.links.learn.asynchronousWork.discoverJavaScriptTimers": "Discover JavaScript Timers",
+  "components.header.links.learn.asynchronousWork.understandingProcessnexttick": "Understanding process.nextTick()",
+  "components.header.links.learn.asynchronousWork.understandingSetimmediate": "Understanding setImmediate()",
+  "components.header.links.learn.asynchronousWork.theNodejsEventEmitter": "The Node.js Event emitter",
+  "components.header.links.learn.manipulatingFiles": "Manipulating Files",
+  "components.header.links.learn.manipulatingFiles.nodejsFileStats": "Node.js file stats",
+  "components.header.links.learn.manipulatingFiles.nodejsFilePaths": "Node.js File Paths",
+  "components.header.links.learn.manipulatingFiles.workingWithFileDescriptorsInNodejs": "Working with file descriptors in Node.js",
+  "components.header.links.learn.manipulatingFiles.readingFilesWithNodejs": "Reading files with Node.js",
+  "components.header.links.learn.manipulatingFiles.writingFilesWithNodejs": "Writing files with Node.js",
+  "components.header.links.learn.manipulatingFiles.workingWithFoldersInNodejs": "Working with folders in Node.js",
+  "components.header.links.learn.commandLine": "Command Line",
+  "components.header.links.learn.commandLine.runNodejsScriptsFromTheCommandLine": "Run Node.js scripts from the command line",
+  "components.header.links.learn.commandLine.howToReadEnvironmentVariablesFromNodejs": "How to read environment variables from Node.js",
+  "components.header.links.learn.commandLine.howToUseTheNodejsRepl": "How to use the Node.js REPL",
+  "components.header.links.learn.commandLine.outputToTheCommandLineUsingNodejs": "Output to the command line using Node.js",
+  "components.header.links.learn.commandLine.acceptInputFromTheCommandLineInNodejs": "Accept input from the command line in Node.js"
 }
diff --git a/i18n/locales/es.json b/i18n/locales/es.json
index bf5ff792c29c0..c421b79c69435 100644
--- a/i18n/locales/es.json
+++ b/i18n/locales/es.json
@@ -18,7 +18,7 @@
   "components.navigation.docs.links.es6": "ES6 and beyond",
   "components.navigation.docs.links.apiLts": "{fullLtsNodeVersion} API {spanLts}",
   "components.navigation.docs.links.apiCurrent": "{fullCurrentNodeVersion} API",
-  "components.navigation.docs.links.guides": "Guides",
+  "components.navigation.docs.links.guides": "Guides {spanGuides}",
   "components.navigation.docs.links.dependencies": "Dependencies",
   "components.navigation.getInvolved.links.collabSummit": "Collab Summit",
   "components.navigation.getInvolved.links.contribute": "Contribute",
@@ -69,9 +69,42 @@
   "components.common.card.announcement": "Announcements",
   "components.common.card.release": "Releases",
   "components.common.card.vulnerability": "Vulnerabilities",
-  "components.home.homeDownloadButton.download": "Download {version} {isLts, select, true {lts} other {current}}",
+  "components.home.homeDownloadButton.download": "{version} {isLts, select, true {LTS} other {Current}}",
   "components.home.homeDownloadButton.tagline": "{isLts, select, true {Recommended For Most Users} other {Latest Features}}",
   "components.home.homeDownloadButton.changelog": "Changelog",
   "components.home.homeDownloadButton.otherDownloads": "Other Downloads",
-  "components.home.homeDownloadButton.apiDocs": "API Docs"
+  "components.home.homeDownloadButton.apiDocs": "API Docs",
+  "components.header.links.learn": "Learn",
+  "components.header.links.learn.gettingStarted": "Getting Started",
+  "components.header.links.learn.gettingStarted.introductionToNodejs": "Introduction to Node.js",
+  "components.header.links.learn.gettingStarted.howToInstallNodejs": "How to install Node.js",
+  "components.header.links.learn.gettingStarted.howMuchJavascriptDoYouNeedToKnowToUseNodejs": "How much JavaScript do you need to know to use Node.js?",
+  "components.header.links.learn.gettingStarted.differencesBetweenNodejsAndTheBrowser": "Differences between Node.js and the Browser",
+  "components.header.links.learn.gettingStarted.theV8JavascriptEngine": "The V8 JavaScript Engine",
+  "components.header.links.learn.gettingStarted.anIntroductionToTheNpmPackageManager": "An introduction to the NPM package manager",
+  "components.header.links.learn.gettingStarted.ecmascript2015Es6AndBeyond": "ECMAScript 2015 (ES6) and beyond",
+  "components.header.links.learn.gettingStarted.nodejsTheDifferenceBetweenDevelopmentAndProduction": "Node.js, the difference between development and production",
+  "components.header.links.learn.gettingStarted.nodejsWithTypescript": "Node.js with TypeScript",
+  "components.header.links.learn.gettingStarted.nodejsWithWebassembly": "Node.js with WebAssembly",
+  "components.header.links.learn.asynchronousWork": "Asynchronous Work",
+  "components.header.links.learn.asynchronousWork.asynchronousFlowControl": "Asynchronous flow control",
+  "components.header.links.learn.asynchronousWork.overviewOfBlockingVsNonBlocking": "Overview of Blocking vs Non-Blocking",
+  "components.header.links.learn.asynchronousWork.javascriptAsynchronousProgrammingAndCallbacks": "JavaScript Asynchronous Programming and Callbacks",
+  "components.header.links.learn.asynchronousWork.discoverJavaScriptTimers": "Discover JavaScript Timers",
+  "components.header.links.learn.asynchronousWork.understandingProcessnexttick": "Understanding process.nextTick()",
+  "components.header.links.learn.asynchronousWork.understandingSetimmediate": "Understanding setImmediate()",
+  "components.header.links.learn.asynchronousWork.theNodejsEventEmitter": "The Node.js Event emitter",
+  "components.header.links.learn.manipulatingFiles": "Manipulating Files",
+  "components.header.links.learn.manipulatingFiles.nodejsFileStats": "Node.js file stats",
+  "components.header.links.learn.manipulatingFiles.nodejsFilePaths": "Node.js File Paths",
+  "components.header.links.learn.manipulatingFiles.workingWithFileDescriptorsInNodejs": "Working with file descriptors in Node.js",
+  "components.header.links.learn.manipulatingFiles.readingFilesWithNodejs": "Reading files with Node.js",
+  "components.header.links.learn.manipulatingFiles.writingFilesWithNodejs": "Writing files with Node.js",
+  "components.header.links.learn.manipulatingFiles.workingWithFoldersInNodejs": "Working with folders in Node.js",
+  "components.header.links.learn.commandLine": "Command Line",
+  "components.header.links.learn.commandLine.runNodejsScriptsFromTheCommandLine": "Run Node.js scripts from the command line",
+  "components.header.links.learn.commandLine.howToReadEnvironmentVariablesFromNodejs": "How to read environment variables from Node.js",
+  "components.header.links.learn.commandLine.howToUseTheNodejsRepl": "How to use the Node.js REPL",
+  "components.header.links.learn.commandLine.outputToTheCommandLineUsingNodejs": "Output to the command line using Node.js",
+  "components.header.links.learn.commandLine.acceptInputFromTheCommandLineInNodejs": "Accept input from the command line in Node.js"
 }
diff --git a/i18n/locales/fr.json b/i18n/locales/fr.json
index bf5ff792c29c0..c421b79c69435 100644
--- a/i18n/locales/fr.json
+++ b/i18n/locales/fr.json
@@ -18,7 +18,7 @@
   "components.navigation.docs.links.es6": "ES6 and beyond",
   "components.navigation.docs.links.apiLts": "{fullLtsNodeVersion} API {spanLts}",
   "components.navigation.docs.links.apiCurrent": "{fullCurrentNodeVersion} API",
-  "components.navigation.docs.links.guides": "Guides",
+  "components.navigation.docs.links.guides": "Guides {spanGuides}",
   "components.navigation.docs.links.dependencies": "Dependencies",
   "components.navigation.getInvolved.links.collabSummit": "Collab Summit",
   "components.navigation.getInvolved.links.contribute": "Contribute",
@@ -69,9 +69,42 @@
   "components.common.card.announcement": "Announcements",
   "components.common.card.release": "Releases",
   "components.common.card.vulnerability": "Vulnerabilities",
-  "components.home.homeDownloadButton.download": "Download {version} {isLts, select, true {lts} other {current}}",
+  "components.home.homeDownloadButton.download": "{version} {isLts, select, true {LTS} other {Current}}",
   "components.home.homeDownloadButton.tagline": "{isLts, select, true {Recommended For Most Users} other {Latest Features}}",
   "components.home.homeDownloadButton.changelog": "Changelog",
   "components.home.homeDownloadButton.otherDownloads": "Other Downloads",
-  "components.home.homeDownloadButton.apiDocs": "API Docs"
+  "components.home.homeDownloadButton.apiDocs": "API Docs",
+  "components.header.links.learn": "Learn",
+  "components.header.links.learn.gettingStarted": "Getting Started",
+  "components.header.links.learn.gettingStarted.introductionToNodejs": "Introduction to Node.js",
+  "components.header.links.learn.gettingStarted.howToInstallNodejs": "How to install Node.js",
+  "components.header.links.learn.gettingStarted.howMuchJavascriptDoYouNeedToKnowToUseNodejs": "How much JavaScript do you need to know to use Node.js?",
+  "components.header.links.learn.gettingStarted.differencesBetweenNodejsAndTheBrowser": "Differences between Node.js and the Browser",
+  "components.header.links.learn.gettingStarted.theV8JavascriptEngine": "The V8 JavaScript Engine",
+  "components.header.links.learn.gettingStarted.anIntroductionToTheNpmPackageManager": "An introduction to the NPM package manager",
+  "components.header.links.learn.gettingStarted.ecmascript2015Es6AndBeyond": "ECMAScript 2015 (ES6) and beyond",
+  "components.header.links.learn.gettingStarted.nodejsTheDifferenceBetweenDevelopmentAndProduction": "Node.js, the difference between development and production",
+  "components.header.links.learn.gettingStarted.nodejsWithTypescript": "Node.js with TypeScript",
+  "components.header.links.learn.gettingStarted.nodejsWithWebassembly": "Node.js with WebAssembly",
+  "components.header.links.learn.asynchronousWork": "Asynchronous Work",
+  "components.header.links.learn.asynchronousWork.asynchronousFlowControl": "Asynchronous flow control",
+  "components.header.links.learn.asynchronousWork.overviewOfBlockingVsNonBlocking": "Overview of Blocking vs Non-Blocking",
+  "components.header.links.learn.asynchronousWork.javascriptAsynchronousProgrammingAndCallbacks": "JavaScript Asynchronous Programming and Callbacks",
+  "components.header.links.learn.asynchronousWork.discoverJavaScriptTimers": "Discover JavaScript Timers",
+  "components.header.links.learn.asynchronousWork.understandingProcessnexttick": "Understanding process.nextTick()",
+  "components.header.links.learn.asynchronousWork.understandingSetimmediate": "Understanding setImmediate()",
+  "components.header.links.learn.asynchronousWork.theNodejsEventEmitter": "The Node.js Event emitter",
+  "components.header.links.learn.manipulatingFiles": "Manipulating Files",
+  "components.header.links.learn.manipulatingFiles.nodejsFileStats": "Node.js file stats",
+  "components.header.links.learn.manipulatingFiles.nodejsFilePaths": "Node.js File Paths",
+  "components.header.links.learn.manipulatingFiles.workingWithFileDescriptorsInNodejs": "Working with file descriptors in Node.js",
+  "components.header.links.learn.manipulatingFiles.readingFilesWithNodejs": "Reading files with Node.js",
+  "components.header.links.learn.manipulatingFiles.writingFilesWithNodejs": "Writing files with Node.js",
+  "components.header.links.learn.manipulatingFiles.workingWithFoldersInNodejs": "Working with folders in Node.js",
+  "components.header.links.learn.commandLine": "Command Line",
+  "components.header.links.learn.commandLine.runNodejsScriptsFromTheCommandLine": "Run Node.js scripts from the command line",
+  "components.header.links.learn.commandLine.howToReadEnvironmentVariablesFromNodejs": "How to read environment variables from Node.js",
+  "components.header.links.learn.commandLine.howToUseTheNodejsRepl": "How to use the Node.js REPL",
+  "components.header.links.learn.commandLine.outputToTheCommandLineUsingNodejs": "Output to the command line using Node.js",
+  "components.header.links.learn.commandLine.acceptInputFromTheCommandLineInNodejs": "Accept input from the command line in Node.js"
 }
diff --git a/i18n/locales/id.json b/i18n/locales/id.json
index bf5ff792c29c0..c421b79c69435 100644
--- a/i18n/locales/id.json
+++ b/i18n/locales/id.json
@@ -18,7 +18,7 @@
   "components.navigation.docs.links.es6": "ES6 and beyond",
   "components.navigation.docs.links.apiLts": "{fullLtsNodeVersion} API {spanLts}",
   "components.navigation.docs.links.apiCurrent": "{fullCurrentNodeVersion} API",
-  "components.navigation.docs.links.guides": "Guides",
+  "components.navigation.docs.links.guides": "Guides {spanGuides}",
   "components.navigation.docs.links.dependencies": "Dependencies",
   "components.navigation.getInvolved.links.collabSummit": "Collab Summit",
   "components.navigation.getInvolved.links.contribute": "Contribute",
@@ -69,9 +69,42 @@
   "components.common.card.announcement": "Announcements",
   "components.common.card.release": "Releases",
   "components.common.card.vulnerability": "Vulnerabilities",
-  "components.home.homeDownloadButton.download": "Download {version} {isLts, select, true {lts} other {current}}",
+  "components.home.homeDownloadButton.download": "{version} {isLts, select, true {LTS} other {Current}}",
   "components.home.homeDownloadButton.tagline": "{isLts, select, true {Recommended For Most Users} other {Latest Features}}",
   "components.home.homeDownloadButton.changelog": "Changelog",
   "components.home.homeDownloadButton.otherDownloads": "Other Downloads",
-  "components.home.homeDownloadButton.apiDocs": "API Docs"
+  "components.home.homeDownloadButton.apiDocs": "API Docs",
+  "components.header.links.learn": "Learn",
+  "components.header.links.learn.gettingStarted": "Getting Started",
+  "components.header.links.learn.gettingStarted.introductionToNodejs": "Introduction to Node.js",
+  "components.header.links.learn.gettingStarted.howToInstallNodejs": "How to install Node.js",
+  "components.header.links.learn.gettingStarted.howMuchJavascriptDoYouNeedToKnowToUseNodejs": "How much JavaScript do you need to know to use Node.js?",
+  "components.header.links.learn.gettingStarted.differencesBetweenNodejsAndTheBrowser": "Differences between Node.js and the Browser",
+  "components.header.links.learn.gettingStarted.theV8JavascriptEngine": "The V8 JavaScript Engine",
+  "components.header.links.learn.gettingStarted.anIntroductionToTheNpmPackageManager": "An introduction to the NPM package manager",
+  "components.header.links.learn.gettingStarted.ecmascript2015Es6AndBeyond": "ECMAScript 2015 (ES6) and beyond",
+  "components.header.links.learn.gettingStarted.nodejsTheDifferenceBetweenDevelopmentAndProduction": "Node.js, the difference between development and production",
+  "components.header.links.learn.gettingStarted.nodejsWithTypescript": "Node.js with TypeScript",
+  "components.header.links.learn.gettingStarted.nodejsWithWebassembly": "Node.js with WebAssembly",
+  "components.header.links.learn.asynchronousWork": "Asynchronous Work",
+  "components.header.links.learn.asynchronousWork.asynchronousFlowControl": "Asynchronous flow control",
+  "components.header.links.learn.asynchronousWork.overviewOfBlockingVsNonBlocking": "Overview of Blocking vs Non-Blocking",
+  "components.header.links.learn.asynchronousWork.javascriptAsynchronousProgrammingAndCallbacks": "JavaScript Asynchronous Programming and Callbacks",
+  "components.header.links.learn.asynchronousWork.discoverJavaScriptTimers": "Discover JavaScript Timers",
+  "components.header.links.learn.asynchronousWork.understandingProcessnexttick": "Understanding process.nextTick()",
+  "components.header.links.learn.asynchronousWork.understandingSetimmediate": "Understanding setImmediate()",
+  "components.header.links.learn.asynchronousWork.theNodejsEventEmitter": "The Node.js Event emitter",
+  "components.header.links.learn.manipulatingFiles": "Manipulating Files",
+  "components.header.links.learn.manipulatingFiles.nodejsFileStats": "Node.js file stats",
+  "components.header.links.learn.manipulatingFiles.nodejsFilePaths": "Node.js File Paths",
+  "components.header.links.learn.manipulatingFiles.workingWithFileDescriptorsInNodejs": "Working with file descriptors in Node.js",
+  "components.header.links.learn.manipulatingFiles.readingFilesWithNodejs": "Reading files with Node.js",
+  "components.header.links.learn.manipulatingFiles.writingFilesWithNodejs": "Writing files with Node.js",
+  "components.header.links.learn.manipulatingFiles.workingWithFoldersInNodejs": "Working with folders in Node.js",
+  "components.header.links.learn.commandLine": "Command Line",
+  "components.header.links.learn.commandLine.runNodejsScriptsFromTheCommandLine": "Run Node.js scripts from the command line",
+  "components.header.links.learn.commandLine.howToReadEnvironmentVariablesFromNodejs": "How to read environment variables from Node.js",
+  "components.header.links.learn.commandLine.howToUseTheNodejsRepl": "How to use the Node.js REPL",
+  "components.header.links.learn.commandLine.outputToTheCommandLineUsingNodejs": "Output to the command line using Node.js",
+  "components.header.links.learn.commandLine.acceptInputFromTheCommandLineInNodejs": "Accept input from the command line in Node.js"
 }
diff --git a/i18n/locales/it.json b/i18n/locales/it.json
index bf5ff792c29c0..c421b79c69435 100644
--- a/i18n/locales/it.json
+++ b/i18n/locales/it.json
@@ -18,7 +18,7 @@
   "components.navigation.docs.links.es6": "ES6 and beyond",
   "components.navigation.docs.links.apiLts": "{fullLtsNodeVersion} API {spanLts}",
   "components.navigation.docs.links.apiCurrent": "{fullCurrentNodeVersion} API",
-  "components.navigation.docs.links.guides": "Guides",
+  "components.navigation.docs.links.guides": "Guides {spanGuides}",
   "components.navigation.docs.links.dependencies": "Dependencies",
   "components.navigation.getInvolved.links.collabSummit": "Collab Summit",
   "components.navigation.getInvolved.links.contribute": "Contribute",
@@ -69,9 +69,42 @@
   "components.common.card.announcement": "Announcements",
   "components.common.card.release": "Releases",
   "components.common.card.vulnerability": "Vulnerabilities",
-  "components.home.homeDownloadButton.download": "Download {version} {isLts, select, true {lts} other {current}}",
+  "components.home.homeDownloadButton.download": "{version} {isLts, select, true {LTS} other {Current}}",
   "components.home.homeDownloadButton.tagline": "{isLts, select, true {Recommended For Most Users} other {Latest Features}}",
   "components.home.homeDownloadButton.changelog": "Changelog",
   "components.home.homeDownloadButton.otherDownloads": "Other Downloads",
-  "components.home.homeDownloadButton.apiDocs": "API Docs"
+  "components.home.homeDownloadButton.apiDocs": "API Docs",
+  "components.header.links.learn": "Learn",
+  "components.header.links.learn.gettingStarted": "Getting Started",
+  "components.header.links.learn.gettingStarted.introductionToNodejs": "Introduction to Node.js",
+  "components.header.links.learn.gettingStarted.howToInstallNodejs": "How to install Node.js",
+  "components.header.links.learn.gettingStarted.howMuchJavascriptDoYouNeedToKnowToUseNodejs": "How much JavaScript do you need to know to use Node.js?",
+  "components.header.links.learn.gettingStarted.differencesBetweenNodejsAndTheBrowser": "Differences between Node.js and the Browser",
+  "components.header.links.learn.gettingStarted.theV8JavascriptEngine": "The V8 JavaScript Engine",
+  "components.header.links.learn.gettingStarted.anIntroductionToTheNpmPackageManager": "An introduction to the NPM package manager",
+  "components.header.links.learn.gettingStarted.ecmascript2015Es6AndBeyond": "ECMAScript 2015 (ES6) and beyond",
+  "components.header.links.learn.gettingStarted.nodejsTheDifferenceBetweenDevelopmentAndProduction": "Node.js, the difference between development and production",
+  "components.header.links.learn.gettingStarted.nodejsWithTypescript": "Node.js with TypeScript",
+  "components.header.links.learn.gettingStarted.nodejsWithWebassembly": "Node.js with WebAssembly",
+  "components.header.links.learn.asynchronousWork": "Asynchronous Work",
+  "components.header.links.learn.asynchronousWork.asynchronousFlowControl": "Asynchronous flow control",
+  "components.header.links.learn.asynchronousWork.overviewOfBlockingVsNonBlocking": "Overview of Blocking vs Non-Blocking",
+  "components.header.links.learn.asynchronousWork.javascriptAsynchronousProgrammingAndCallbacks": "JavaScript Asynchronous Programming and Callbacks",
+  "components.header.links.learn.asynchronousWork.discoverJavaScriptTimers": "Discover JavaScript Timers",
+  "components.header.links.learn.asynchronousWork.understandingProcessnexttick": "Understanding process.nextTick()",
+  "components.header.links.learn.asynchronousWork.understandingSetimmediate": "Understanding setImmediate()",
+  "components.header.links.learn.asynchronousWork.theNodejsEventEmitter": "The Node.js Event emitter",
+  "components.header.links.learn.manipulatingFiles": "Manipulating Files",
+  "components.header.links.learn.manipulatingFiles.nodejsFileStats": "Node.js file stats",
+  "components.header.links.learn.manipulatingFiles.nodejsFilePaths": "Node.js File Paths",
+  "components.header.links.learn.manipulatingFiles.workingWithFileDescriptorsInNodejs": "Working with file descriptors in Node.js",
+  "components.header.links.learn.manipulatingFiles.readingFilesWithNodejs": "Reading files with Node.js",
+  "components.header.links.learn.manipulatingFiles.writingFilesWithNodejs": "Writing files with Node.js",
+  "components.header.links.learn.manipulatingFiles.workingWithFoldersInNodejs": "Working with folders in Node.js",
+  "components.header.links.learn.commandLine": "Command Line",
+  "components.header.links.learn.commandLine.runNodejsScriptsFromTheCommandLine": "Run Node.js scripts from the command line",
+  "components.header.links.learn.commandLine.howToReadEnvironmentVariablesFromNodejs": "How to read environment variables from Node.js",
+  "components.header.links.learn.commandLine.howToUseTheNodejsRepl": "How to use the Node.js REPL",
+  "components.header.links.learn.commandLine.outputToTheCommandLineUsingNodejs": "Output to the command line using Node.js",
+  "components.header.links.learn.commandLine.acceptInputFromTheCommandLineInNodejs": "Accept input from the command line in Node.js"
 }
diff --git a/i18n/locales/ja.json b/i18n/locales/ja.json
index bf5ff792c29c0..c421b79c69435 100644
--- a/i18n/locales/ja.json
+++ b/i18n/locales/ja.json
@@ -18,7 +18,7 @@
   "components.navigation.docs.links.es6": "ES6 and beyond",
   "components.navigation.docs.links.apiLts": "{fullLtsNodeVersion} API {spanLts}",
   "components.navigation.docs.links.apiCurrent": "{fullCurrentNodeVersion} API",
-  "components.navigation.docs.links.guides": "Guides",
+  "components.navigation.docs.links.guides": "Guides {spanGuides}",
   "components.navigation.docs.links.dependencies": "Dependencies",
   "components.navigation.getInvolved.links.collabSummit": "Collab Summit",
   "components.navigation.getInvolved.links.contribute": "Contribute",
@@ -69,9 +69,42 @@
   "components.common.card.announcement": "Announcements",
   "components.common.card.release": "Releases",
   "components.common.card.vulnerability": "Vulnerabilities",
-  "components.home.homeDownloadButton.download": "Download {version} {isLts, select, true {lts} other {current}}",
+  "components.home.homeDownloadButton.download": "{version} {isLts, select, true {LTS} other {Current}}",
   "components.home.homeDownloadButton.tagline": "{isLts, select, true {Recommended For Most Users} other {Latest Features}}",
   "components.home.homeDownloadButton.changelog": "Changelog",
   "components.home.homeDownloadButton.otherDownloads": "Other Downloads",
-  "components.home.homeDownloadButton.apiDocs": "API Docs"
+  "components.home.homeDownloadButton.apiDocs": "API Docs",
+  "components.header.links.learn": "Learn",
+  "components.header.links.learn.gettingStarted": "Getting Started",
+  "components.header.links.learn.gettingStarted.introductionToNodejs": "Introduction to Node.js",
+  "components.header.links.learn.gettingStarted.howToInstallNodejs": "How to install Node.js",
+  "components.header.links.learn.gettingStarted.howMuchJavascriptDoYouNeedToKnowToUseNodejs": "How much JavaScript do you need to know to use Node.js?",
+  "components.header.links.learn.gettingStarted.differencesBetweenNodejsAndTheBrowser": "Differences between Node.js and the Browser",
+  "components.header.links.learn.gettingStarted.theV8JavascriptEngine": "The V8 JavaScript Engine",
+  "components.header.links.learn.gettingStarted.anIntroductionToTheNpmPackageManager": "An introduction to the NPM package manager",
+  "components.header.links.learn.gettingStarted.ecmascript2015Es6AndBeyond": "ECMAScript 2015 (ES6) and beyond",
+  "components.header.links.learn.gettingStarted.nodejsTheDifferenceBetweenDevelopmentAndProduction": "Node.js, the difference between development and production",
+  "components.header.links.learn.gettingStarted.nodejsWithTypescript": "Node.js with TypeScript",
+  "components.header.links.learn.gettingStarted.nodejsWithWebassembly": "Node.js with WebAssembly",
+  "components.header.links.learn.asynchronousWork": "Asynchronous Work",
+  "components.header.links.learn.asynchronousWork.asynchronousFlowControl": "Asynchronous flow control",
+  "components.header.links.learn.asynchronousWork.overviewOfBlockingVsNonBlocking": "Overview of Blocking vs Non-Blocking",
+  "components.header.links.learn.asynchronousWork.javascriptAsynchronousProgrammingAndCallbacks": "JavaScript Asynchronous Programming and Callbacks",
+  "components.header.links.learn.asynchronousWork.discoverJavaScriptTimers": "Discover JavaScript Timers",
+  "components.header.links.learn.asynchronousWork.understandingProcessnexttick": "Understanding process.nextTick()",
+  "components.header.links.learn.asynchronousWork.understandingSetimmediate": "Understanding setImmediate()",
+  "components.header.links.learn.asynchronousWork.theNodejsEventEmitter": "The Node.js Event emitter",
+  "components.header.links.learn.manipulatingFiles": "Manipulating Files",
+  "components.header.links.learn.manipulatingFiles.nodejsFileStats": "Node.js file stats",
+  "components.header.links.learn.manipulatingFiles.nodejsFilePaths": "Node.js File Paths",
+  "components.header.links.learn.manipulatingFiles.workingWithFileDescriptorsInNodejs": "Working with file descriptors in Node.js",
+  "components.header.links.learn.manipulatingFiles.readingFilesWithNodejs": "Reading files with Node.js",
+  "components.header.links.learn.manipulatingFiles.writingFilesWithNodejs": "Writing files with Node.js",
+  "components.header.links.learn.manipulatingFiles.workingWithFoldersInNodejs": "Working with folders in Node.js",
+  "components.header.links.learn.commandLine": "Command Line",
+  "components.header.links.learn.commandLine.runNodejsScriptsFromTheCommandLine": "Run Node.js scripts from the command line",
+  "components.header.links.learn.commandLine.howToReadEnvironmentVariablesFromNodejs": "How to read environment variables from Node.js",
+  "components.header.links.learn.commandLine.howToUseTheNodejsRepl": "How to use the Node.js REPL",
+  "components.header.links.learn.commandLine.outputToTheCommandLineUsingNodejs": "Output to the command line using Node.js",
+  "components.header.links.learn.commandLine.acceptInputFromTheCommandLineInNodejs": "Accept input from the command line in Node.js"
 }
diff --git a/i18n/locales/ka.json b/i18n/locales/ka.json
index bf5ff792c29c0..c421b79c69435 100644
--- a/i18n/locales/ka.json
+++ b/i18n/locales/ka.json
@@ -18,7 +18,7 @@
   "components.navigation.docs.links.es6": "ES6 and beyond",
   "components.navigation.docs.links.apiLts": "{fullLtsNodeVersion} API {spanLts}",
   "components.navigation.docs.links.apiCurrent": "{fullCurrentNodeVersion} API",
-  "components.navigation.docs.links.guides": "Guides",
+  "components.navigation.docs.links.guides": "Guides {spanGuides}",
   "components.navigation.docs.links.dependencies": "Dependencies",
   "components.navigation.getInvolved.links.collabSummit": "Collab Summit",
   "components.navigation.getInvolved.links.contribute": "Contribute",
@@ -69,9 +69,42 @@
   "components.common.card.announcement": "Announcements",
   "components.common.card.release": "Releases",
   "components.common.card.vulnerability": "Vulnerabilities",
-  "components.home.homeDownloadButton.download": "Download {version} {isLts, select, true {lts} other {current}}",
+  "components.home.homeDownloadButton.download": "{version} {isLts, select, true {LTS} other {Current}}",
   "components.home.homeDownloadButton.tagline": "{isLts, select, true {Recommended For Most Users} other {Latest Features}}",
   "components.home.homeDownloadButton.changelog": "Changelog",
   "components.home.homeDownloadButton.otherDownloads": "Other Downloads",
-  "components.home.homeDownloadButton.apiDocs": "API Docs"
+  "components.home.homeDownloadButton.apiDocs": "API Docs",
+  "components.header.links.learn": "Learn",
+  "components.header.links.learn.gettingStarted": "Getting Started",
+  "components.header.links.learn.gettingStarted.introductionToNodejs": "Introduction to Node.js",
+  "components.header.links.learn.gettingStarted.howToInstallNodejs": "How to install Node.js",
+  "components.header.links.learn.gettingStarted.howMuchJavascriptDoYouNeedToKnowToUseNodejs": "How much JavaScript do you need to know to use Node.js?",
+  "components.header.links.learn.gettingStarted.differencesBetweenNodejsAndTheBrowser": "Differences between Node.js and the Browser",
+  "components.header.links.learn.gettingStarted.theV8JavascriptEngine": "The V8 JavaScript Engine",
+  "components.header.links.learn.gettingStarted.anIntroductionToTheNpmPackageManager": "An introduction to the NPM package manager",
+  "components.header.links.learn.gettingStarted.ecmascript2015Es6AndBeyond": "ECMAScript 2015 (ES6) and beyond",
+  "components.header.links.learn.gettingStarted.nodejsTheDifferenceBetweenDevelopmentAndProduction": "Node.js, the difference between development and production",
+  "components.header.links.learn.gettingStarted.nodejsWithTypescript": "Node.js with TypeScript",
+  "components.header.links.learn.gettingStarted.nodejsWithWebassembly": "Node.js with WebAssembly",
+  "components.header.links.learn.asynchronousWork": "Asynchronous Work",
+  "components.header.links.learn.asynchronousWork.asynchronousFlowControl": "Asynchronous flow control",
+  "components.header.links.learn.asynchronousWork.overviewOfBlockingVsNonBlocking": "Overview of Blocking vs Non-Blocking",
+  "components.header.links.learn.asynchronousWork.javascriptAsynchronousProgrammingAndCallbacks": "JavaScript Asynchronous Programming and Callbacks",
+  "components.header.links.learn.asynchronousWork.discoverJavaScriptTimers": "Discover JavaScript Timers",
+  "components.header.links.learn.asynchronousWork.understandingProcessnexttick": "Understanding process.nextTick()",
+  "components.header.links.learn.asynchronousWork.understandingSetimmediate": "Understanding setImmediate()",
+  "components.header.links.learn.asynchronousWork.theNodejsEventEmitter": "The Node.js Event emitter",
+  "components.header.links.learn.manipulatingFiles": "Manipulating Files",
+  "components.header.links.learn.manipulatingFiles.nodejsFileStats": "Node.js file stats",
+  "components.header.links.learn.manipulatingFiles.nodejsFilePaths": "Node.js File Paths",
+  "components.header.links.learn.manipulatingFiles.workingWithFileDescriptorsInNodejs": "Working with file descriptors in Node.js",
+  "components.header.links.learn.manipulatingFiles.readingFilesWithNodejs": "Reading files with Node.js",
+  "components.header.links.learn.manipulatingFiles.writingFilesWithNodejs": "Writing files with Node.js",
+  "components.header.links.learn.manipulatingFiles.workingWithFoldersInNodejs": "Working with folders in Node.js",
+  "components.header.links.learn.commandLine": "Command Line",
+  "components.header.links.learn.commandLine.runNodejsScriptsFromTheCommandLine": "Run Node.js scripts from the command line",
+  "components.header.links.learn.commandLine.howToReadEnvironmentVariablesFromNodejs": "How to read environment variables from Node.js",
+  "components.header.links.learn.commandLine.howToUseTheNodejsRepl": "How to use the Node.js REPL",
+  "components.header.links.learn.commandLine.outputToTheCommandLineUsingNodejs": "Output to the command line using Node.js",
+  "components.header.links.learn.commandLine.acceptInputFromTheCommandLineInNodejs": "Accept input from the command line in Node.js"
 }
diff --git a/i18n/locales/ko.json b/i18n/locales/ko.json
index bf5ff792c29c0..c421b79c69435 100644
--- a/i18n/locales/ko.json
+++ b/i18n/locales/ko.json
@@ -18,7 +18,7 @@
   "components.navigation.docs.links.es6": "ES6 and beyond",
   "components.navigation.docs.links.apiLts": "{fullLtsNodeVersion} API {spanLts}",
   "components.navigation.docs.links.apiCurrent": "{fullCurrentNodeVersion} API",
-  "components.navigation.docs.links.guides": "Guides",
+  "components.navigation.docs.links.guides": "Guides {spanGuides}",
   "components.navigation.docs.links.dependencies": "Dependencies",
   "components.navigation.getInvolved.links.collabSummit": "Collab Summit",
   "components.navigation.getInvolved.links.contribute": "Contribute",
@@ -69,9 +69,42 @@
   "components.common.card.announcement": "Announcements",
   "components.common.card.release": "Releases",
   "components.common.card.vulnerability": "Vulnerabilities",
-  "components.home.homeDownloadButton.download": "Download {version} {isLts, select, true {lts} other {current}}",
+  "components.home.homeDownloadButton.download": "{version} {isLts, select, true {LTS} other {Current}}",
   "components.home.homeDownloadButton.tagline": "{isLts, select, true {Recommended For Most Users} other {Latest Features}}",
   "components.home.homeDownloadButton.changelog": "Changelog",
   "components.home.homeDownloadButton.otherDownloads": "Other Downloads",
-  "components.home.homeDownloadButton.apiDocs": "API Docs"
+  "components.home.homeDownloadButton.apiDocs": "API Docs",
+  "components.header.links.learn": "Learn",
+  "components.header.links.learn.gettingStarted": "Getting Started",
+  "components.header.links.learn.gettingStarted.introductionToNodejs": "Introduction to Node.js",
+  "components.header.links.learn.gettingStarted.howToInstallNodejs": "How to install Node.js",
+  "components.header.links.learn.gettingStarted.howMuchJavascriptDoYouNeedToKnowToUseNodejs": "How much JavaScript do you need to know to use Node.js?",
+  "components.header.links.learn.gettingStarted.differencesBetweenNodejsAndTheBrowser": "Differences between Node.js and the Browser",
+  "components.header.links.learn.gettingStarted.theV8JavascriptEngine": "The V8 JavaScript Engine",
+  "components.header.links.learn.gettingStarted.anIntroductionToTheNpmPackageManager": "An introduction to the NPM package manager",
+  "components.header.links.learn.gettingStarted.ecmascript2015Es6AndBeyond": "ECMAScript 2015 (ES6) and beyond",
+  "components.header.links.learn.gettingStarted.nodejsTheDifferenceBetweenDevelopmentAndProduction": "Node.js, the difference between development and production",
+  "components.header.links.learn.gettingStarted.nodejsWithTypescript": "Node.js with TypeScript",
+  "components.header.links.learn.gettingStarted.nodejsWithWebassembly": "Node.js with WebAssembly",
+  "components.header.links.learn.asynchronousWork": "Asynchronous Work",
+  "components.header.links.learn.asynchronousWork.asynchronousFlowControl": "Asynchronous flow control",
+  "components.header.links.learn.asynchronousWork.overviewOfBlockingVsNonBlocking": "Overview of Blocking vs Non-Blocking",
+  "components.header.links.learn.asynchronousWork.javascriptAsynchronousProgrammingAndCallbacks": "JavaScript Asynchronous Programming and Callbacks",
+  "components.header.links.learn.asynchronousWork.discoverJavaScriptTimers": "Discover JavaScript Timers",
+  "components.header.links.learn.asynchronousWork.understandingProcessnexttick": "Understanding process.nextTick()",
+  "components.header.links.learn.asynchronousWork.understandingSetimmediate": "Understanding setImmediate()",
+  "components.header.links.learn.asynchronousWork.theNodejsEventEmitter": "The Node.js Event emitter",
+  "components.header.links.learn.manipulatingFiles": "Manipulating Files",
+  "components.header.links.learn.manipulatingFiles.nodejsFileStats": "Node.js file stats",
+  "components.header.links.learn.manipulatingFiles.nodejsFilePaths": "Node.js File Paths",
+  "components.header.links.learn.manipulatingFiles.workingWithFileDescriptorsInNodejs": "Working with file descriptors in Node.js",
+  "components.header.links.learn.manipulatingFiles.readingFilesWithNodejs": "Reading files with Node.js",
+  "components.header.links.learn.manipulatingFiles.writingFilesWithNodejs": "Writing files with Node.js",
+  "components.header.links.learn.manipulatingFiles.workingWithFoldersInNodejs": "Working with folders in Node.js",
+  "components.header.links.learn.commandLine": "Command Line",
+  "components.header.links.learn.commandLine.runNodejsScriptsFromTheCommandLine": "Run Node.js scripts from the command line",
+  "components.header.links.learn.commandLine.howToReadEnvironmentVariablesFromNodejs": "How to read environment variables from Node.js",
+  "components.header.links.learn.commandLine.howToUseTheNodejsRepl": "How to use the Node.js REPL",
+  "components.header.links.learn.commandLine.outputToTheCommandLineUsingNodejs": "Output to the command line using Node.js",
+  "components.header.links.learn.commandLine.acceptInputFromTheCommandLineInNodejs": "Accept input from the command line in Node.js"
 }
diff --git a/i18n/locales/pt-br.json b/i18n/locales/pt-br.json
index bf5ff792c29c0..c421b79c69435 100644
--- a/i18n/locales/pt-br.json
+++ b/i18n/locales/pt-br.json
@@ -18,7 +18,7 @@
   "components.navigation.docs.links.es6": "ES6 and beyond",
   "components.navigation.docs.links.apiLts": "{fullLtsNodeVersion} API {spanLts}",
   "components.navigation.docs.links.apiCurrent": "{fullCurrentNodeVersion} API",
-  "components.navigation.docs.links.guides": "Guides",
+  "components.navigation.docs.links.guides": "Guides {spanGuides}",
   "components.navigation.docs.links.dependencies": "Dependencies",
   "components.navigation.getInvolved.links.collabSummit": "Collab Summit",
   "components.navigation.getInvolved.links.contribute": "Contribute",
@@ -69,9 +69,42 @@
   "components.common.card.announcement": "Announcements",
   "components.common.card.release": "Releases",
   "components.common.card.vulnerability": "Vulnerabilities",
-  "components.home.homeDownloadButton.download": "Download {version} {isLts, select, true {lts} other {current}}",
+  "components.home.homeDownloadButton.download": "{version} {isLts, select, true {LTS} other {Current}}",
   "components.home.homeDownloadButton.tagline": "{isLts, select, true {Recommended For Most Users} other {Latest Features}}",
   "components.home.homeDownloadButton.changelog": "Changelog",
   "components.home.homeDownloadButton.otherDownloads": "Other Downloads",
-  "components.home.homeDownloadButton.apiDocs": "API Docs"
+  "components.home.homeDownloadButton.apiDocs": "API Docs",
+  "components.header.links.learn": "Learn",
+  "components.header.links.learn.gettingStarted": "Getting Started",
+  "components.header.links.learn.gettingStarted.introductionToNodejs": "Introduction to Node.js",
+  "components.header.links.learn.gettingStarted.howToInstallNodejs": "How to install Node.js",
+  "components.header.links.learn.gettingStarted.howMuchJavascriptDoYouNeedToKnowToUseNodejs": "How much JavaScript do you need to know to use Node.js?",
+  "components.header.links.learn.gettingStarted.differencesBetweenNodejsAndTheBrowser": "Differences between Node.js and the Browser",
+  "components.header.links.learn.gettingStarted.theV8JavascriptEngine": "The V8 JavaScript Engine",
+  "components.header.links.learn.gettingStarted.anIntroductionToTheNpmPackageManager": "An introduction to the NPM package manager",
+  "components.header.links.learn.gettingStarted.ecmascript2015Es6AndBeyond": "ECMAScript 2015 (ES6) and beyond",
+  "components.header.links.learn.gettingStarted.nodejsTheDifferenceBetweenDevelopmentAndProduction": "Node.js, the difference between development and production",
+  "components.header.links.learn.gettingStarted.nodejsWithTypescript": "Node.js with TypeScript",
+  "components.header.links.learn.gettingStarted.nodejsWithWebassembly": "Node.js with WebAssembly",
+  "components.header.links.learn.asynchronousWork": "Asynchronous Work",
+  "components.header.links.learn.asynchronousWork.asynchronousFlowControl": "Asynchronous flow control",
+  "components.header.links.learn.asynchronousWork.overviewOfBlockingVsNonBlocking": "Overview of Blocking vs Non-Blocking",
+  "components.header.links.learn.asynchronousWork.javascriptAsynchronousProgrammingAndCallbacks": "JavaScript Asynchronous Programming and Callbacks",
+  "components.header.links.learn.asynchronousWork.discoverJavaScriptTimers": "Discover JavaScript Timers",
+  "components.header.links.learn.asynchronousWork.understandingProcessnexttick": "Understanding process.nextTick()",
+  "components.header.links.learn.asynchronousWork.understandingSetimmediate": "Understanding setImmediate()",
+  "components.header.links.learn.asynchronousWork.theNodejsEventEmitter": "The Node.js Event emitter",
+  "components.header.links.learn.manipulatingFiles": "Manipulating Files",
+  "components.header.links.learn.manipulatingFiles.nodejsFileStats": "Node.js file stats",
+  "components.header.links.learn.manipulatingFiles.nodejsFilePaths": "Node.js File Paths",
+  "components.header.links.learn.manipulatingFiles.workingWithFileDescriptorsInNodejs": "Working with file descriptors in Node.js",
+  "components.header.links.learn.manipulatingFiles.readingFilesWithNodejs": "Reading files with Node.js",
+  "components.header.links.learn.manipulatingFiles.writingFilesWithNodejs": "Writing files with Node.js",
+  "components.header.links.learn.manipulatingFiles.workingWithFoldersInNodejs": "Working with folders in Node.js",
+  "components.header.links.learn.commandLine": "Command Line",
+  "components.header.links.learn.commandLine.runNodejsScriptsFromTheCommandLine": "Run Node.js scripts from the command line",
+  "components.header.links.learn.commandLine.howToReadEnvironmentVariablesFromNodejs": "How to read environment variables from Node.js",
+  "components.header.links.learn.commandLine.howToUseTheNodejsRepl": "How to use the Node.js REPL",
+  "components.header.links.learn.commandLine.outputToTheCommandLineUsingNodejs": "Output to the command line using Node.js",
+  "components.header.links.learn.commandLine.acceptInputFromTheCommandLineInNodejs": "Accept input from the command line in Node.js"
 }
diff --git a/i18n/locales/ru.json b/i18n/locales/ru.json
index bf5ff792c29c0..c421b79c69435 100644
--- a/i18n/locales/ru.json
+++ b/i18n/locales/ru.json
@@ -18,7 +18,7 @@
   "components.navigation.docs.links.es6": "ES6 and beyond",
   "components.navigation.docs.links.apiLts": "{fullLtsNodeVersion} API {spanLts}",
   "components.navigation.docs.links.apiCurrent": "{fullCurrentNodeVersion} API",
-  "components.navigation.docs.links.guides": "Guides",
+  "components.navigation.docs.links.guides": "Guides {spanGuides}",
   "components.navigation.docs.links.dependencies": "Dependencies",
   "components.navigation.getInvolved.links.collabSummit": "Collab Summit",
   "components.navigation.getInvolved.links.contribute": "Contribute",
@@ -69,9 +69,42 @@
   "components.common.card.announcement": "Announcements",
   "components.common.card.release": "Releases",
   "components.common.card.vulnerability": "Vulnerabilities",
-  "components.home.homeDownloadButton.download": "Download {version} {isLts, select, true {lts} other {current}}",
+  "components.home.homeDownloadButton.download": "{version} {isLts, select, true {LTS} other {Current}}",
   "components.home.homeDownloadButton.tagline": "{isLts, select, true {Recommended For Most Users} other {Latest Features}}",
   "components.home.homeDownloadButton.changelog": "Changelog",
   "components.home.homeDownloadButton.otherDownloads": "Other Downloads",
-  "components.home.homeDownloadButton.apiDocs": "API Docs"
+  "components.home.homeDownloadButton.apiDocs": "API Docs",
+  "components.header.links.learn": "Learn",
+  "components.header.links.learn.gettingStarted": "Getting Started",
+  "components.header.links.learn.gettingStarted.introductionToNodejs": "Introduction to Node.js",
+  "components.header.links.learn.gettingStarted.howToInstallNodejs": "How to install Node.js",
+  "components.header.links.learn.gettingStarted.howMuchJavascriptDoYouNeedToKnowToUseNodejs": "How much JavaScript do you need to know to use Node.js?",
+  "components.header.links.learn.gettingStarted.differencesBetweenNodejsAndTheBrowser": "Differences between Node.js and the Browser",
+  "components.header.links.learn.gettingStarted.theV8JavascriptEngine": "The V8 JavaScript Engine",
+  "components.header.links.learn.gettingStarted.anIntroductionToTheNpmPackageManager": "An introduction to the NPM package manager",
+  "components.header.links.learn.gettingStarted.ecmascript2015Es6AndBeyond": "ECMAScript 2015 (ES6) and beyond",
+  "components.header.links.learn.gettingStarted.nodejsTheDifferenceBetweenDevelopmentAndProduction": "Node.js, the difference between development and production",
+  "components.header.links.learn.gettingStarted.nodejsWithTypescript": "Node.js with TypeScript",
+  "components.header.links.learn.gettingStarted.nodejsWithWebassembly": "Node.js with WebAssembly",
+  "components.header.links.learn.asynchronousWork": "Asynchronous Work",
+  "components.header.links.learn.asynchronousWork.asynchronousFlowControl": "Asynchronous flow control",
+  "components.header.links.learn.asynchronousWork.overviewOfBlockingVsNonBlocking": "Overview of Blocking vs Non-Blocking",
+  "components.header.links.learn.asynchronousWork.javascriptAsynchronousProgrammingAndCallbacks": "JavaScript Asynchronous Programming and Callbacks",
+  "components.header.links.learn.asynchronousWork.discoverJavaScriptTimers": "Discover JavaScript Timers",
+  "components.header.links.learn.asynchronousWork.understandingProcessnexttick": "Understanding process.nextTick()",
+  "components.header.links.learn.asynchronousWork.understandingSetimmediate": "Understanding setImmediate()",
+  "components.header.links.learn.asynchronousWork.theNodejsEventEmitter": "The Node.js Event emitter",
+  "components.header.links.learn.manipulatingFiles": "Manipulating Files",
+  "components.header.links.learn.manipulatingFiles.nodejsFileStats": "Node.js file stats",
+  "components.header.links.learn.manipulatingFiles.nodejsFilePaths": "Node.js File Paths",
+  "components.header.links.learn.manipulatingFiles.workingWithFileDescriptorsInNodejs": "Working with file descriptors in Node.js",
+  "components.header.links.learn.manipulatingFiles.readingFilesWithNodejs": "Reading files with Node.js",
+  "components.header.links.learn.manipulatingFiles.writingFilesWithNodejs": "Writing files with Node.js",
+  "components.header.links.learn.manipulatingFiles.workingWithFoldersInNodejs": "Working with folders in Node.js",
+  "components.header.links.learn.commandLine": "Command Line",
+  "components.header.links.learn.commandLine.runNodejsScriptsFromTheCommandLine": "Run Node.js scripts from the command line",
+  "components.header.links.learn.commandLine.howToReadEnvironmentVariablesFromNodejs": "How to read environment variables from Node.js",
+  "components.header.links.learn.commandLine.howToUseTheNodejsRepl": "How to use the Node.js REPL",
+  "components.header.links.learn.commandLine.outputToTheCommandLineUsingNodejs": "Output to the command line using Node.js",
+  "components.header.links.learn.commandLine.acceptInputFromTheCommandLineInNodejs": "Accept input from the command line in Node.js"
 }
diff --git a/i18n/locales/tr.json b/i18n/locales/tr.json
index bf5ff792c29c0..c421b79c69435 100644
--- a/i18n/locales/tr.json
+++ b/i18n/locales/tr.json
@@ -18,7 +18,7 @@
   "components.navigation.docs.links.es6": "ES6 and beyond",
   "components.navigation.docs.links.apiLts": "{fullLtsNodeVersion} API {spanLts}",
   "components.navigation.docs.links.apiCurrent": "{fullCurrentNodeVersion} API",
-  "components.navigation.docs.links.guides": "Guides",
+  "components.navigation.docs.links.guides": "Guides {spanGuides}",
   "components.navigation.docs.links.dependencies": "Dependencies",
   "components.navigation.getInvolved.links.collabSummit": "Collab Summit",
   "components.navigation.getInvolved.links.contribute": "Contribute",
@@ -69,9 +69,42 @@
   "components.common.card.announcement": "Announcements",
   "components.common.card.release": "Releases",
   "components.common.card.vulnerability": "Vulnerabilities",
-  "components.home.homeDownloadButton.download": "Download {version} {isLts, select, true {lts} other {current}}",
+  "components.home.homeDownloadButton.download": "{version} {isLts, select, true {LTS} other {Current}}",
   "components.home.homeDownloadButton.tagline": "{isLts, select, true {Recommended For Most Users} other {Latest Features}}",
   "components.home.homeDownloadButton.changelog": "Changelog",
   "components.home.homeDownloadButton.otherDownloads": "Other Downloads",
-  "components.home.homeDownloadButton.apiDocs": "API Docs"
+  "components.home.homeDownloadButton.apiDocs": "API Docs",
+  "components.header.links.learn": "Learn",
+  "components.header.links.learn.gettingStarted": "Getting Started",
+  "components.header.links.learn.gettingStarted.introductionToNodejs": "Introduction to Node.js",
+  "components.header.links.learn.gettingStarted.howToInstallNodejs": "How to install Node.js",
+  "components.header.links.learn.gettingStarted.howMuchJavascriptDoYouNeedToKnowToUseNodejs": "How much JavaScript do you need to know to use Node.js?",
+  "components.header.links.learn.gettingStarted.differencesBetweenNodejsAndTheBrowser": "Differences between Node.js and the Browser",
+  "components.header.links.learn.gettingStarted.theV8JavascriptEngine": "The V8 JavaScript Engine",
+  "components.header.links.learn.gettingStarted.anIntroductionToTheNpmPackageManager": "An introduction to the NPM package manager",
+  "components.header.links.learn.gettingStarted.ecmascript2015Es6AndBeyond": "ECMAScript 2015 (ES6) and beyond",
+  "components.header.links.learn.gettingStarted.nodejsTheDifferenceBetweenDevelopmentAndProduction": "Node.js, the difference between development and production",
+  "components.header.links.learn.gettingStarted.nodejsWithTypescript": "Node.js with TypeScript",
+  "components.header.links.learn.gettingStarted.nodejsWithWebassembly": "Node.js with WebAssembly",
+  "components.header.links.learn.asynchronousWork": "Asynchronous Work",
+  "components.header.links.learn.asynchronousWork.asynchronousFlowControl": "Asynchronous flow control",
+  "components.header.links.learn.asynchronousWork.overviewOfBlockingVsNonBlocking": "Overview of Blocking vs Non-Blocking",
+  "components.header.links.learn.asynchronousWork.javascriptAsynchronousProgrammingAndCallbacks": "JavaScript Asynchronous Programming and Callbacks",
+  "components.header.links.learn.asynchronousWork.discoverJavaScriptTimers": "Discover JavaScript Timers",
+  "components.header.links.learn.asynchronousWork.understandingProcessnexttick": "Understanding process.nextTick()",
+  "components.header.links.learn.asynchronousWork.understandingSetimmediate": "Understanding setImmediate()",
+  "components.header.links.learn.asynchronousWork.theNodejsEventEmitter": "The Node.js Event emitter",
+  "components.header.links.learn.manipulatingFiles": "Manipulating Files",
+  "components.header.links.learn.manipulatingFiles.nodejsFileStats": "Node.js file stats",
+  "components.header.links.learn.manipulatingFiles.nodejsFilePaths": "Node.js File Paths",
+  "components.header.links.learn.manipulatingFiles.workingWithFileDescriptorsInNodejs": "Working with file descriptors in Node.js",
+  "components.header.links.learn.manipulatingFiles.readingFilesWithNodejs": "Reading files with Node.js",
+  "components.header.links.learn.manipulatingFiles.writingFilesWithNodejs": "Writing files with Node.js",
+  "components.header.links.learn.manipulatingFiles.workingWithFoldersInNodejs": "Working with folders in Node.js",
+  "components.header.links.learn.commandLine": "Command Line",
+  "components.header.links.learn.commandLine.runNodejsScriptsFromTheCommandLine": "Run Node.js scripts from the command line",
+  "components.header.links.learn.commandLine.howToReadEnvironmentVariablesFromNodejs": "How to read environment variables from Node.js",
+  "components.header.links.learn.commandLine.howToUseTheNodejsRepl": "How to use the Node.js REPL",
+  "components.header.links.learn.commandLine.outputToTheCommandLineUsingNodejs": "Output to the command line using Node.js",
+  "components.header.links.learn.commandLine.acceptInputFromTheCommandLineInNodejs": "Accept input from the command line in Node.js"
 }
diff --git a/i18n/locales/uk.json b/i18n/locales/uk.json
index bf5ff792c29c0..c421b79c69435 100644
--- a/i18n/locales/uk.json
+++ b/i18n/locales/uk.json
@@ -18,7 +18,7 @@
   "components.navigation.docs.links.es6": "ES6 and beyond",
   "components.navigation.docs.links.apiLts": "{fullLtsNodeVersion} API {spanLts}",
   "components.navigation.docs.links.apiCurrent": "{fullCurrentNodeVersion} API",
-  "components.navigation.docs.links.guides": "Guides",
+  "components.navigation.docs.links.guides": "Guides {spanGuides}",
   "components.navigation.docs.links.dependencies": "Dependencies",
   "components.navigation.getInvolved.links.collabSummit": "Collab Summit",
   "components.navigation.getInvolved.links.contribute": "Contribute",
@@ -69,9 +69,42 @@
   "components.common.card.announcement": "Announcements",
   "components.common.card.release": "Releases",
   "components.common.card.vulnerability": "Vulnerabilities",
-  "components.home.homeDownloadButton.download": "Download {version} {isLts, select, true {lts} other {current}}",
+  "components.home.homeDownloadButton.download": "{version} {isLts, select, true {LTS} other {Current}}",
   "components.home.homeDownloadButton.tagline": "{isLts, select, true {Recommended For Most Users} other {Latest Features}}",
   "components.home.homeDownloadButton.changelog": "Changelog",
   "components.home.homeDownloadButton.otherDownloads": "Other Downloads",
-  "components.home.homeDownloadButton.apiDocs": "API Docs"
+  "components.home.homeDownloadButton.apiDocs": "API Docs",
+  "components.header.links.learn": "Learn",
+  "components.header.links.learn.gettingStarted": "Getting Started",
+  "components.header.links.learn.gettingStarted.introductionToNodejs": "Introduction to Node.js",
+  "components.header.links.learn.gettingStarted.howToInstallNodejs": "How to install Node.js",
+  "components.header.links.learn.gettingStarted.howMuchJavascriptDoYouNeedToKnowToUseNodejs": "How much JavaScript do you need to know to use Node.js?",
+  "components.header.links.learn.gettingStarted.differencesBetweenNodejsAndTheBrowser": "Differences between Node.js and the Browser",
+  "components.header.links.learn.gettingStarted.theV8JavascriptEngine": "The V8 JavaScript Engine",
+  "components.header.links.learn.gettingStarted.anIntroductionToTheNpmPackageManager": "An introduction to the NPM package manager",
+  "components.header.links.learn.gettingStarted.ecmascript2015Es6AndBeyond": "ECMAScript 2015 (ES6) and beyond",
+  "components.header.links.learn.gettingStarted.nodejsTheDifferenceBetweenDevelopmentAndProduction": "Node.js, the difference between development and production",
+  "components.header.links.learn.gettingStarted.nodejsWithTypescript": "Node.js with TypeScript",
+  "components.header.links.learn.gettingStarted.nodejsWithWebassembly": "Node.js with WebAssembly",
+  "components.header.links.learn.asynchronousWork": "Asynchronous Work",
+  "components.header.links.learn.asynchronousWork.asynchronousFlowControl": "Asynchronous flow control",
+  "components.header.links.learn.asynchronousWork.overviewOfBlockingVsNonBlocking": "Overview of Blocking vs Non-Blocking",
+  "components.header.links.learn.asynchronousWork.javascriptAsynchronousProgrammingAndCallbacks": "JavaScript Asynchronous Programming and Callbacks",
+  "components.header.links.learn.asynchronousWork.discoverJavaScriptTimers": "Discover JavaScript Timers",
+  "components.header.links.learn.asynchronousWork.understandingProcessnexttick": "Understanding process.nextTick()",
+  "components.header.links.learn.asynchronousWork.understandingSetimmediate": "Understanding setImmediate()",
+  "components.header.links.learn.asynchronousWork.theNodejsEventEmitter": "The Node.js Event emitter",
+  "components.header.links.learn.manipulatingFiles": "Manipulating Files",
+  "components.header.links.learn.manipulatingFiles.nodejsFileStats": "Node.js file stats",
+  "components.header.links.learn.manipulatingFiles.nodejsFilePaths": "Node.js File Paths",
+  "components.header.links.learn.manipulatingFiles.workingWithFileDescriptorsInNodejs": "Working with file descriptors in Node.js",
+  "components.header.links.learn.manipulatingFiles.readingFilesWithNodejs": "Reading files with Node.js",
+  "components.header.links.learn.manipulatingFiles.writingFilesWithNodejs": "Writing files with Node.js",
+  "components.header.links.learn.manipulatingFiles.workingWithFoldersInNodejs": "Working with folders in Node.js",
+  "components.header.links.learn.commandLine": "Command Line",
+  "components.header.links.learn.commandLine.runNodejsScriptsFromTheCommandLine": "Run Node.js scripts from the command line",
+  "components.header.links.learn.commandLine.howToReadEnvironmentVariablesFromNodejs": "How to read environment variables from Node.js",
+  "components.header.links.learn.commandLine.howToUseTheNodejsRepl": "How to use the Node.js REPL",
+  "components.header.links.learn.commandLine.outputToTheCommandLineUsingNodejs": "Output to the command line using Node.js",
+  "components.header.links.learn.commandLine.acceptInputFromTheCommandLineInNodejs": "Accept input from the command line in Node.js"
 }
diff --git a/i18n/locales/zh-cn.json b/i18n/locales/zh-cn.json
index bf5ff792c29c0..c421b79c69435 100644
--- a/i18n/locales/zh-cn.json
+++ b/i18n/locales/zh-cn.json
@@ -18,7 +18,7 @@
   "components.navigation.docs.links.es6": "ES6 and beyond",
   "components.navigation.docs.links.apiLts": "{fullLtsNodeVersion} API {spanLts}",
   "components.navigation.docs.links.apiCurrent": "{fullCurrentNodeVersion} API",
-  "components.navigation.docs.links.guides": "Guides",
+  "components.navigation.docs.links.guides": "Guides {spanGuides}",
   "components.navigation.docs.links.dependencies": "Dependencies",
   "components.navigation.getInvolved.links.collabSummit": "Collab Summit",
   "components.navigation.getInvolved.links.contribute": "Contribute",
@@ -69,9 +69,42 @@
   "components.common.card.announcement": "Announcements",
   "components.common.card.release": "Releases",
   "components.common.card.vulnerability": "Vulnerabilities",
-  "components.home.homeDownloadButton.download": "Download {version} {isLts, select, true {lts} other {current}}",
+  "components.home.homeDownloadButton.download": "{version} {isLts, select, true {LTS} other {Current}}",
   "components.home.homeDownloadButton.tagline": "{isLts, select, true {Recommended For Most Users} other {Latest Features}}",
   "components.home.homeDownloadButton.changelog": "Changelog",
   "components.home.homeDownloadButton.otherDownloads": "Other Downloads",
-  "components.home.homeDownloadButton.apiDocs": "API Docs"
+  "components.home.homeDownloadButton.apiDocs": "API Docs",
+  "components.header.links.learn": "Learn",
+  "components.header.links.learn.gettingStarted": "Getting Started",
+  "components.header.links.learn.gettingStarted.introductionToNodejs": "Introduction to Node.js",
+  "components.header.links.learn.gettingStarted.howToInstallNodejs": "How to install Node.js",
+  "components.header.links.learn.gettingStarted.howMuchJavascriptDoYouNeedToKnowToUseNodejs": "How much JavaScript do you need to know to use Node.js?",
+  "components.header.links.learn.gettingStarted.differencesBetweenNodejsAndTheBrowser": "Differences between Node.js and the Browser",
+  "components.header.links.learn.gettingStarted.theV8JavascriptEngine": "The V8 JavaScript Engine",
+  "components.header.links.learn.gettingStarted.anIntroductionToTheNpmPackageManager": "An introduction to the NPM package manager",
+  "components.header.links.learn.gettingStarted.ecmascript2015Es6AndBeyond": "ECMAScript 2015 (ES6) and beyond",
+  "components.header.links.learn.gettingStarted.nodejsTheDifferenceBetweenDevelopmentAndProduction": "Node.js, the difference between development and production",
+  "components.header.links.learn.gettingStarted.nodejsWithTypescript": "Node.js with TypeScript",
+  "components.header.links.learn.gettingStarted.nodejsWithWebassembly": "Node.js with WebAssembly",
+  "components.header.links.learn.asynchronousWork": "Asynchronous Work",
+  "components.header.links.learn.asynchronousWork.asynchronousFlowControl": "Asynchronous flow control",
+  "components.header.links.learn.asynchronousWork.overviewOfBlockingVsNonBlocking": "Overview of Blocking vs Non-Blocking",
+  "components.header.links.learn.asynchronousWork.javascriptAsynchronousProgrammingAndCallbacks": "JavaScript Asynchronous Programming and Callbacks",
+  "components.header.links.learn.asynchronousWork.discoverJavaScriptTimers": "Discover JavaScript Timers",
+  "components.header.links.learn.asynchronousWork.understandingProcessnexttick": "Understanding process.nextTick()",
+  "components.header.links.learn.asynchronousWork.understandingSetimmediate": "Understanding setImmediate()",
+  "components.header.links.learn.asynchronousWork.theNodejsEventEmitter": "The Node.js Event emitter",
+  "components.header.links.learn.manipulatingFiles": "Manipulating Files",
+  "components.header.links.learn.manipulatingFiles.nodejsFileStats": "Node.js file stats",
+  "components.header.links.learn.manipulatingFiles.nodejsFilePaths": "Node.js File Paths",
+  "components.header.links.learn.manipulatingFiles.workingWithFileDescriptorsInNodejs": "Working with file descriptors in Node.js",
+  "components.header.links.learn.manipulatingFiles.readingFilesWithNodejs": "Reading files with Node.js",
+  "components.header.links.learn.manipulatingFiles.writingFilesWithNodejs": "Writing files with Node.js",
+  "components.header.links.learn.manipulatingFiles.workingWithFoldersInNodejs": "Working with folders in Node.js",
+  "components.header.links.learn.commandLine": "Command Line",
+  "components.header.links.learn.commandLine.runNodejsScriptsFromTheCommandLine": "Run Node.js scripts from the command line",
+  "components.header.links.learn.commandLine.howToReadEnvironmentVariablesFromNodejs": "How to read environment variables from Node.js",
+  "components.header.links.learn.commandLine.howToUseTheNodejsRepl": "How to use the Node.js REPL",
+  "components.header.links.learn.commandLine.outputToTheCommandLineUsingNodejs": "Output to the command line using Node.js",
+  "components.header.links.learn.commandLine.acceptInputFromTheCommandLineInNodejs": "Accept input from the command line in Node.js"
 }
diff --git a/i18n/locales/zh-tw.json b/i18n/locales/zh-tw.json
index bf5ff792c29c0..c421b79c69435 100644
--- a/i18n/locales/zh-tw.json
+++ b/i18n/locales/zh-tw.json
@@ -18,7 +18,7 @@
   "components.navigation.docs.links.es6": "ES6 and beyond",
   "components.navigation.docs.links.apiLts": "{fullLtsNodeVersion} API {spanLts}",
   "components.navigation.docs.links.apiCurrent": "{fullCurrentNodeVersion} API",
-  "components.navigation.docs.links.guides": "Guides",
+  "components.navigation.docs.links.guides": "Guides {spanGuides}",
   "components.navigation.docs.links.dependencies": "Dependencies",
   "components.navigation.getInvolved.links.collabSummit": "Collab Summit",
   "components.navigation.getInvolved.links.contribute": "Contribute",
@@ -69,9 +69,42 @@
   "components.common.card.announcement": "Announcements",
   "components.common.card.release": "Releases",
   "components.common.card.vulnerability": "Vulnerabilities",
-  "components.home.homeDownloadButton.download": "Download {version} {isLts, select, true {lts} other {current}}",
+  "components.home.homeDownloadButton.download": "{version} {isLts, select, true {LTS} other {Current}}",
   "components.home.homeDownloadButton.tagline": "{isLts, select, true {Recommended For Most Users} other {Latest Features}}",
   "components.home.homeDownloadButton.changelog": "Changelog",
   "components.home.homeDownloadButton.otherDownloads": "Other Downloads",
-  "components.home.homeDownloadButton.apiDocs": "API Docs"
+  "components.home.homeDownloadButton.apiDocs": "API Docs",
+  "components.header.links.learn": "Learn",
+  "components.header.links.learn.gettingStarted": "Getting Started",
+  "components.header.links.learn.gettingStarted.introductionToNodejs": "Introduction to Node.js",
+  "components.header.links.learn.gettingStarted.howToInstallNodejs": "How to install Node.js",
+  "components.header.links.learn.gettingStarted.howMuchJavascriptDoYouNeedToKnowToUseNodejs": "How much JavaScript do you need to know to use Node.js?",
+  "components.header.links.learn.gettingStarted.differencesBetweenNodejsAndTheBrowser": "Differences between Node.js and the Browser",
+  "components.header.links.learn.gettingStarted.theV8JavascriptEngine": "The V8 JavaScript Engine",
+  "components.header.links.learn.gettingStarted.anIntroductionToTheNpmPackageManager": "An introduction to the NPM package manager",
+  "components.header.links.learn.gettingStarted.ecmascript2015Es6AndBeyond": "ECMAScript 2015 (ES6) and beyond",
+  "components.header.links.learn.gettingStarted.nodejsTheDifferenceBetweenDevelopmentAndProduction": "Node.js, the difference between development and production",
+  "components.header.links.learn.gettingStarted.nodejsWithTypescript": "Node.js with TypeScript",
+  "components.header.links.learn.gettingStarted.nodejsWithWebassembly": "Node.js with WebAssembly",
+  "components.header.links.learn.asynchronousWork": "Asynchronous Work",
+  "components.header.links.learn.asynchronousWork.asynchronousFlowControl": "Asynchronous flow control",
+  "components.header.links.learn.asynchronousWork.overviewOfBlockingVsNonBlocking": "Overview of Blocking vs Non-Blocking",
+  "components.header.links.learn.asynchronousWork.javascriptAsynchronousProgrammingAndCallbacks": "JavaScript Asynchronous Programming and Callbacks",
+  "components.header.links.learn.asynchronousWork.discoverJavaScriptTimers": "Discover JavaScript Timers",
+  "components.header.links.learn.asynchronousWork.understandingProcessnexttick": "Understanding process.nextTick()",
+  "components.header.links.learn.asynchronousWork.understandingSetimmediate": "Understanding setImmediate()",
+  "components.header.links.learn.asynchronousWork.theNodejsEventEmitter": "The Node.js Event emitter",
+  "components.header.links.learn.manipulatingFiles": "Manipulating Files",
+  "components.header.links.learn.manipulatingFiles.nodejsFileStats": "Node.js file stats",
+  "components.header.links.learn.manipulatingFiles.nodejsFilePaths": "Node.js File Paths",
+  "components.header.links.learn.manipulatingFiles.workingWithFileDescriptorsInNodejs": "Working with file descriptors in Node.js",
+  "components.header.links.learn.manipulatingFiles.readingFilesWithNodejs": "Reading files with Node.js",
+  "components.header.links.learn.manipulatingFiles.writingFilesWithNodejs": "Writing files with Node.js",
+  "components.header.links.learn.manipulatingFiles.workingWithFoldersInNodejs": "Working with folders in Node.js",
+  "components.header.links.learn.commandLine": "Command Line",
+  "components.header.links.learn.commandLine.runNodejsScriptsFromTheCommandLine": "Run Node.js scripts from the command line",
+  "components.header.links.learn.commandLine.howToReadEnvironmentVariablesFromNodejs": "How to read environment variables from Node.js",
+  "components.header.links.learn.commandLine.howToUseTheNodejsRepl": "How to use the Node.js REPL",
+  "components.header.links.learn.commandLine.outputToTheCommandLineUsingNodejs": "Output to the command line using Node.js",
+  "components.header.links.learn.commandLine.acceptInputFromTheCommandLineInNodejs": "Accept input from the command line in Node.js"
 }
diff --git a/layouts/DocsLayout.tsx b/layouts/DocsLayout.tsx
index 7d865cb627adb..b3a9bbbf09955 100644
--- a/layouts/DocsLayout.tsx
+++ b/layouts/DocsLayout.tsx
@@ -24,6 +24,9 @@ const DocsLayout: FC<PropsWithChildren> = ({ children }) => {
       fullCurrentNodeVersion: current ? current.versionWithPrefix : undefined,
       currentNodeVersion: current ? `v${current.major}.x` : undefined,
     },
+    guides: {
+      spanGuides: <span className="small color-lightgray">ARCHIVE</span>,
+    },
   };
 
   return (
diff --git a/layouts/LearnLayout.tsx b/layouts/LearnLayout.tsx
new file mode 100644
index 0000000000000..1bafc1be61af3
--- /dev/null
+++ b/layouts/LearnLayout.tsx
@@ -0,0 +1,16 @@
+import type { FC, PropsWithChildren } from 'react';
+
+import SideNavigation from '@/components/SideNavigation';
+
+import BaseLayout from './BaseLayout';
+
+const LearnLayout: FC<PropsWithChildren> = ({ children }) => (
+  <BaseLayout>
+    <div className="has-side-nav container">
+      <SideNavigation navigationKey="learn" />
+      <article dir="auto">{children}</article>
+    </div>
+  </BaseLayout>
+);
+
+export default LearnLayout;
diff --git a/navigation.json b/navigation.json
index fe4c4c8b8f6fb..e58e4c02adc51 100644
--- a/navigation.json
+++ b/navigation.json
@@ -17,6 +17,148 @@
       }
     }
   },
+  "learn": {
+    "link": "/learn",
+    "translationId": "components.header.links.learn",
+    "items": {
+      "gettingStarted": {
+        "link": "/learn/getting-started/introduction-to-nodejs",
+        "translationId": "components.header.links.learn.gettingStarted",
+        "items": {
+          "introductionToNodejs": {
+            "link": "/learn/getting-started/introduction-to-nodejs",
+            "translationId": "components.header.links.learn.gettingStarted.introductionToNodejs"
+          },
+          "howToInstallNodejs": {
+            "link": "/learn/getting-started/how-to-install-nodejs",
+            "translationId": "components.header.links.learn.gettingStarted.howToInstallNodejs"
+          },
+          "howMuchJavascriptDoYouNeedToKnowToUseNodejs": {
+            "link": "/learn/getting-started/how-much-javascript-do-you-need-to-know-to-use-nodejs",
+            "translationId": "components.header.links.learn.gettingStarted.howMuchJavascriptDoYouNeedToKnowToUseNodejs"
+          },
+          "differencesBetweenNodejsAndTheBrowser": {
+            "link": "/learn/getting-started/differences-between-nodejs-and-the-browser",
+            "translationId": "components.header.links.learn.gettingStarted.differencesBetweenNodejsAndTheBrowser"
+          },
+          "theV8JavascriptEngine": {
+            "link": "/learn/getting-started/the-v8-javascript-engine",
+            "translationId": "components.header.links.learn.gettingStarted.theV8JavascriptEngine"
+          },
+          "anIntroductionToTheNpmPackageManager": {
+            "link": "/learn/getting-started/an-introduction-to-the-npm-package-manager",
+            "translationId": "components.header.links.learn.gettingStarted.anIntroductionToTheNpmPackageManager"
+          },
+          "ecmascript2015Es6AndBeyond": {
+            "link": "/learn/getting-started/ecmascript-2015-es6-and-beyond",
+            "translationId": "components.header.links.learn.gettingStarted.ecmascript2015Es6AndBeyond"
+          },
+          "nodejsTheDifferenceBetweenDevelopmentAndProduction": {
+            "link": "/learn/getting-started/nodejs-the-difference-between-development-and-production",
+            "translationId": "components.header.links.learn.gettingStarted.nodejsTheDifferenceBetweenDevelopmentAndProduction"
+          },
+          "nodejsWithTypescript": {
+            "link": "/learn/getting-started/nodejs-with-typescript",
+            "translationId": "components.header.links.learn.gettingStarted.nodejsWithTypescript"
+          },
+          "nodejsWithWebassembly": {
+            "link": "/learn/getting-started/nodejs-with-webassembly",
+            "translationId": "components.header.links.learn.gettingStarted.nodejsWithWebassembly"
+          }
+        }
+      },
+      "asynchronousWork": {
+        "link": "/learn/asynchronous-work/asynchronous-flow-control",
+        "translationId": "components.header.links.learn.asynchronousWork",
+        "items": {
+          "asynchronousFlowControl": {
+            "link": "/learn/asynchronous-work/asynchronous-flow-control",
+            "translationId": "components.header.links.learn.asynchronousWork.asynchronousFlowControl"
+          },
+          "overviewOfBlockingVsNonBlocking": {
+            "link": "/learn/asynchronous-work/overview-of-blocking-vs-non-blocking",
+            "translationId": "components.header.links.learn.asynchronousWork.overviewOfBlockingVsNonBlocking"
+          },
+          "javascriptAsynchronousProgrammingAndCallbacks": {
+            "link": "/learn/asynchronous-work/javascript-asynchronous-programming-and-callbacks",
+            "translationId": "components.header.links.learn.asynchronousWork.javascriptAsynchronousProgrammingAndCallbacks"
+          },
+          "discoverJavaScriptTimers": {
+            "link": "/learn/asynchronous-work/discover-javascript-timers",
+            "translationId": "components.header.links.learn.asynchronousWork.discoverJavaScriptTimers"
+          },
+          "understandingProcessnexttick": {
+            "link": "/learn/asynchronous-work/understanding-processnexttick",
+            "translationId": "components.header.links.learn.asynchronousWork.understandingProcessnexttick"
+          },
+          "understandingSetimmediate": {
+            "link": "/learn/asynchronous-work/understanding-setimmediate",
+            "translationId": "components.header.links.learn.asynchronousWork.understandingSetimmediate"
+          },
+          "theNodejsEventEmitter": {
+            "link": "/learn/asynchronous-work/the-nodejs-event-emitter",
+            "translationId": "components.header.links.learn.asynchronousWork.theNodejsEventEmitter"
+          }
+        }
+      },
+      "manipulatingFiles": {
+        "link": "/learn/manipulating-files/nodejs-file-stats",
+        "translationId": "components.header.links.learn.manipulatingFiles",
+        "items": {
+          "nodejsFileStats": {
+            "link": "/learn/manipulating-files/nodejs-file-stats",
+            "translationId": "components.header.links.learn.manipulatingFiles.nodejsFileStats"
+          },
+          "nodejsFilePaths": {
+            "link": "/learn/manipulating-files/nodejs-file-paths",
+            "translationId": "components.header.links.learn.manipulatingFiles.nodejsFilePaths"
+          },
+          "workingWithFileDescriptorsInNodejs": {
+            "link": "/learn/manipulating-files/working-with-file-descriptors-in-nodejs",
+            "translationId": "components.header.links.learn.manipulatingFiles.workingWithFileDescriptorsInNodejs"
+          },
+          "readingFilesWithNodejs": {
+            "link": "/learn/manipulating-files/reading-files-with-nodejs",
+            "translationId": "components.header.links.learn.manipulatingFiles.readingFilesWithNodejs"
+          },
+          "writingFilesWithNodejs": {
+            "link": "/learn/manipulating-files/writing-files-with-nodejs",
+            "translationId": "components.header.links.learn.manipulatingFiles.writingFilesWithNodejs"
+          },
+          "workingWithFoldersInNodejs": {
+            "link": "/learn/manipulating-files/working-with-folders-in-nodejs",
+            "translationId": "components.header.links.learn.manipulatingFiles.workingWithFoldersInNodejs"
+          }
+        }
+      },
+      "commandLine": {
+        "link": "/learn/command-line/run-nodejs-scripts-from-the-command-line",
+        "translationId": "components.header.links.learn.commandLine",
+        "items": {
+          "runNodejsScriptsFromTheCommandLine": {
+            "link": "/learn/command-line/run-nodejs-scripts-from-the-command-line",
+            "translationId": "components.header.links.learn.commandLine.runNodejsScriptsFromTheCommandLine"
+          },
+          "howToReadEnvironmentVariablesFromNodejs": {
+            "link": "/learn/command-line/how-to-read-environment-variables-from-nodejs",
+            "translationId": "components.header.links.learn.commandLine.howToReadEnvironmentVariablesFromNodejs"
+          },
+          "howToUseTheNodejsRepl": {
+            "link": "/learn/command-line/how-to-use-the-nodejs-repl",
+            "translationId": "components.header.links.learn.commandLine.howToUseTheNodejsRepl"
+          },
+          "outputToTheCommandLineUsingNodejs": {
+            "link": "/learn/command-line/output-to-the-command-line-using-nodejs",
+            "translationId": "components.header.links.learn.commandLine.outputToTheCommandLineUsingNodejs"
+          },
+          "acceptInputFromTheCommandLineInNodejs": {
+            "link": "/learn/command-line/accept-input-from-the-command-line-in-nodejs",
+            "translationId": "components.header.links.learn.commandLine.acceptInputFromTheCommandLineInNodejs"
+          }
+        }
+      }
+    }
+  },
   "download": {
     "link": "/download",
     "translationId": "components.header.links.download",
diff --git a/package-lock.json b/package-lock.json
index a175f85119b4d..e8a1c96fc82a3 100644
--- a/package-lock.json
+++ b/package-lock.json
@@ -5,7 +5,6 @@
   "requires": true,
   "packages": {
     "": {
-      "name": "nodejs.org",
       "license": "MIT",
       "dependencies": {
         "@heroicons/react": "~2.0.18",
diff --git a/package.json b/package.json
index a7826c16c76ea..c676231957ade 100644
--- a/package.json
+++ b/package.json
@@ -1,5 +1,4 @@
 {
-  "name": "nodejs.org",
   "type": "module",
   "private": true,
   "description": "Nodejs.org Website",
diff --git a/pages/en/docs/guides/buffer-constructor-deprecation.md b/pages/en/docs/guides/buffer-constructor-deprecation.md
deleted file mode 100644
index 1de50cde543cb..0000000000000
--- a/pages/en/docs/guides/buffer-constructor-deprecation.md
+++ /dev/null
@@ -1,280 +0,0 @@
----
-title: Porting to the Buffer.from()/Buffer.alloc() API
-layout: docs.hbs
----
-
-# Porting to the `Buffer.from()`/`Buffer.alloc()` API
-
-## Overview
-
-This guide explains how to migrate to safe `Buffer` constructor methods. The migration fixes the following deprecation warning:
-
-> The Buffer() and new Buffer() constructors are not recommended for use due to security and usability concerns. Please use the new Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() construction methods instead.
-
-- [Variant 1: Drop support for Node.js ≤ 4.4.x and 5.0.0 — 5.9.x](#variant-1) (_recommended_)
-- [Variant 2: Use a polyfill](#variant-2)
-- [Variant 3: Manual detection, with safeguards](#variant-3)
-
-### Finding problematic bits of code using `grep`
-
-Just run `grep -nrE '[^a-zA-Z](Slow)?Buffer\s*\(' --exclude-dir node_modules`.
-
-It will find all the potentially unsafe places in your own code (with some considerably unlikely
-exceptions).
-
-### Finding problematic bits of code using Node.js 8
-
-If you’re using Node.js ≥ 8.0.0 (which is recommended), Node.js exposes multiple options that help with finding the relevant pieces of code:
-
-- `--trace-warnings` will make Node.js show a stack trace for this warning and other warnings that are printed by Node.js.
-- `--trace-deprecation` does the same thing, but only for deprecation warnings.
-- `--pending-deprecation` will show more types of deprecation warnings. In particular, it will show the `Buffer()` deprecation warning, even on Node.js 8.
-
-You can set these flags using environment variables:
-
-```bash
-$ export NODE_OPTIONS='--trace-warnings --pending-deprecation'
-$ cat example.js
-'use strict';
-const foo = new Buffer('foo');
-$ node example.js
-(node:7147) [DEP0005] DeprecationWarning: The Buffer() and new Buffer() constructors are not recommended for use due to security and usability concerns. Please use the new Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() construction methods instead.
-    at showFlaggedDeprecation (buffer.js:127:13)
-    at new Buffer (buffer.js:148:3)
-    at Object.<anonymous> (/path/to/example.js:2:13)
-    [... more stack trace lines ...]
-```
-
-### Finding problematic bits of code using linters
-
-ESLint rules [no-buffer-constructor](https://eslint.org/docs/rules/no-buffer-constructor)
-or
-[node/no-deprecated-api](https://github.com/mysticatea/eslint-plugin-node/blob/master/docs/rules/no-deprecated-api.md)
-also find calls to deprecated `Buffer()` API. Those rules are included in some presets.
-
-There is a drawback, though, that it doesn't always
-[work correctly](https://github.com/chalker/safer-buffer#why-not-safe-buffer) when `Buffer` is
-overridden e.g. with a polyfill, so recommended is a combination of this and some other method
-described above.
-
-## <!--variant-1-->Variant 1: Drop support for Node.js ≤ 4.4.x and 5.0.0 — 5.9.x
-
-This is the recommended solution nowadays that would imply only minimal overhead.
-
-The Node.js 5.x release line has been unsupported since July 2016, and the Node.js 4.x release line reaches its End of Life in April 2018 (→ [Schedule](https://github.com/nodejs/Release#release-schedule)). This means that these versions of Node.js will _not_ receive any updates, even in case of security issues, so using these release lines should be avoided, if at all possible.
-
-What you would do in this case is to convert all `new Buffer()` or `Buffer()` calls to use `Buffer.alloc()` or `Buffer.from()`, in the following way:
-
-- For `new Buffer(number)`, replace it with `Buffer.alloc(number)`.
-- For `new Buffer(string)` (or `new Buffer(string, encoding)`), replace it with `Buffer.from(string)` (or `Buffer.from(string, encoding)`).
-- For all other combinations of arguments (these are much rarer), also replace `new Buffer(...arguments)` with `Buffer.from(...arguments)`.
-
-Note that `Buffer.alloc()` is also _faster_ on the current Node.js versions than
-`new Buffer(size).fill(0)`, which is what you would otherwise need to ensure zero-filling.
-
-Enabling ESLint rule [no-buffer-constructor](https://eslint.org/docs/rules/no-buffer-constructor)
-or
-[node/no-deprecated-api](https://github.com/mysticatea/eslint-plugin-node/blob/master/docs/rules/no-deprecated-api.md)
-is recommended to avoid accidental unsafe `Buffer` API usage.
-
-There is also a [JSCodeshift codemod](https://github.com/joyeecheung/node-dep-codemod#dep005)
-for automatically migrating `Buffer` constructors to `Buffer.alloc()` or `Buffer.from()`.
-Note that it currently only works with cases where the arguments are literals or where the
-constructor is invoked with two arguments.
-
-_If you currently support those older Node.js versions and dropping support for them is not possible, or if you support older branches of your packages, consider using [Variant 2](#variant-2)
-or [Variant 3](#variant-3) on older branches, so people using those older branches will also receive
-the fix. That way, you will eradicate potential issues caused by unguarded `Buffer` API usage and
-your users will not observe a runtime deprecation warning when running your code on Node.js 10._
-
-## <!--variant-2-->Variant 2: Use a polyfill
-
-There are three different polyfills available:
-
-- **[safer-buffer](https://www.npmjs.com/package/safer-buffer)** is a drop-in replacement for the
-  entire `Buffer` API, that will _throw_ when using `new Buffer()`.
-
-  You would take exactly the same steps as in [Variant 1](#variant-1), but with a polyfill
-  `const Buffer = require('safer-buffer').Buffer` in all files where you use the new `Buffer` API.
-
-  Do not use the old `new Buffer()` API. In any files where the line above is added,
-  using old `new Buffer()` API will _throw_.
-
-- **[buffer-from](https://www.npmjs.com/package/buffer-from) and/or
-  [buffer-alloc](https://www.npmjs.com/package/buffer-alloc)** are
-  [ponyfills](https://ponyfill.com/) for their respective part of the `Buffer` API. You only need
-  to add the package(s) corresponding to the API you are using.
-
-  You would import the module needed with an appropriate name, e.g.
-  `const bufferFrom = require('buffer-from')` and then use that instead of the call to
-  `new Buffer()`, e.g. `new Buffer('test')` becomes `bufferFrom('test')`.
-
-  A downside with this approach is slightly more code changes to migrate off them (as you would be
-  using e.g. `Buffer.from()` under a different name).
-
-- **[safe-buffer](https://www.npmjs.com/package/safe-buffer)** is also a drop-in replacement for
-  the entire `Buffer` API, but using `new Buffer()` will still work as before.
-
-  A downside to this approach is that it will allow you to also use the older `new Buffer()` API
-  in your code, which is problematic since it can cause issues in your code, and will start
-  emitting runtime deprecation warnings starting with Node.js 10
-  ([read more here](https://github.com/chalker/safer-buffer#why-not-safe-buffer)).
-
-Note that in either case, it is important that you also remove all calls to the old `Buffer`
-API manually — just throwing in `safe-buffer` doesn't fix the problem by itself, it just provides
-a polyfill for the new API. I have seen people doing that mistake.
-
-Enabling ESLint rule [no-buffer-constructor](https://eslint.org/docs/rules/no-buffer-constructor)
-or
-[node/no-deprecated-api](https://github.com/mysticatea/eslint-plugin-node/blob/master/docs/rules/no-deprecated-api.md)
-is recommended.
-
-_Don't forget to drop the polyfill usage once you drop support for Node.js < 4.5.0._
-
-## <!--variant-3-->Variant 3 — Manual detection, with safeguards
-
-This is useful if you create `Buffer` instances in only a few places (e.g. one), or you have your own
-wrapper around them.
-
-### `Buffer(0)`
-
-This special case for creating empty buffers can be safely replaced with `Buffer.concat([])`, which
-returns the same result all the way down to Node.js 0.8.x.
-
-### `Buffer(notNumber)`
-
-Before:
-
-```js
-const buf = new Buffer(notNumber, encoding);
-```
-
-After:
-
-```js
-let buf;
-if (Buffer.from && Buffer.from !== Uint8Array.from) {
-  buf = Buffer.from(notNumber, encoding);
-} else {
-  if (typeof notNumber === 'number') {
-    throw new Error('The "size" argument must be not of type number.');
-  }
-  buf = new Buffer(notNumber, encoding);
-}
-```
-
-`encoding` is optional.
-
-Note that the `typeof notNumber` before `new Buffer()` is required (for cases when `notNumber` argument is not
-hard-coded) and _is not caused by the deprecation of `Buffer` constructor_ — it's exactly _why_ the
-`Buffer` constructor is deprecated. Ecosystem packages lacking this type-check caused numerous
-security issues — situations when unsanitized user input could end up in the `Buffer(arg)` create
-problems ranging from DoS to leaking sensitive information to the attacker from the process memory.
-
-When `notNumber` argument is hardcoded (e.g. literal `"abc"` or `[0,1,2]`), the `typeof` check can
-be omitted.
-
-Also, note that using TypeScript does not fix this problem for you — when libs written in
-`TypeScript` are used from JS, or when user input ends up there — it behaves exactly as pure JS, as
-all type checks are translation-time only and are not present in the actual JS code which TS
-compiles to.
-
-### `Buffer(number)`
-
-For Node.js 0.10.x (and below) support:
-
-```js
-let buf;
-if (Buffer.alloc) {
-  buf = Buffer.alloc(number);
-} else {
-  buf = new Buffer(number);
-  buf.fill(0);
-}
-```
-
-Otherwise (Node.js ≥ 0.12.x):
-
-```js
-const buf = Buffer.alloc ? Buffer.alloc(number) : new Buffer(number).fill(0);
-```
-
-## Regarding `Buffer.allocUnsafe()`
-
-Be extra cautious when using `Buffer.allocUnsafe()`:
-
-- Don't use it if you don't have a good reason to
-  - e.g. you probably won't ever see a performance difference for small buffers, in fact, those
-    might be even faster with `Buffer.alloc()`,
-  - if your code is not in the hot code path — you also probably won't notice a difference,
-  - keep in mind that zero-filling minimizes the potential risks.
-- If you use it, make sure that you never return the buffer in a partially-filled state,
-  - if you are writing to it sequentially — always truncate it to the actual written length
-
-Errors in handling buffers allocated with `Buffer.allocUnsafe()` could result in various issues,
-ranged from undefined behavior of your code to sensitive data (user input, passwords, certs)
-leaking to the remote attacker.
-
-_Note that the same applies to `new Buffer()` usage without zero-filling, depending on the Node.js
-version (and lacking type checks also adds DoS to the list of potential problems)._
-
-## FAQ
-
-### <!--design-flaws-->What is wrong with the `Buffer` constructor?
-
-The `Buffer` constructor could be used to create a buffer in many different ways:
-
-- `new Buffer(42)` creates a `Buffer` of 42 bytes. Before Node.js 8, this buffer contained
-  _arbitrary memory_ for performance reasons, which could include anything ranging from
-  program source code to passwords and encryption keys.
-- `new Buffer('abc')` creates a `Buffer` that contains the UTF-8-encoded version of
-  the string `'abc'`. A second argument could specify another encoding: for example,
-  `new Buffer(string, 'base64')` could be used to convert a Base64 string into the original
-  sequence of bytes that it represents.
-- There are several other combinations of arguments.
-
-This meant that in code like `var buffer = new Buffer(foo);`, _it is not possible to tell
-what exactly the contents of the generated buffer are_ without knowing the type of `foo`.
-
-Sometimes, the value of `foo` comes from an external source. For example, this function
-could be exposed as a service on a web server, converting a UTF-8 string into its Base64 form:
-
-```js
-function stringToBase64(req, res) {
-  // The request body should have the format of `{ string: 'foobar' }`.
-  const rawBytes = new Buffer(req.body.string);
-  const encoded = rawBytes.toString('base64');
-  res.end({ encoded });
-}
-```
-
-Note that this code does _not_ validate the type of `req.body.string`:
-
-- `req.body.string` is expected to be a string. If this is the case, all goes well.
-- `req.body.string` is controlled by the client that sends the request.
-- If `req.body.string` is the _number_ `50`, the `rawBytes` would be `50` bytes:
-  - Before Node.js 8, the content would be uninitialized
-  - After Node.js 8, the content would be `50` bytes with the value `0`
-
-Because of the missing type check, an attacker could intentionally send a number
-as part of the request. Using this, they can either:
-
-- Read uninitialized memory. This **will** leak passwords, encryption keys and other
-  kinds of sensitive information. (Information leak)
-- Force the program to allocate a large amount of memory. For example, when specifying
-  `500000000` as the input value, each request will allocate 500MB of memory.
-  This can be used to either exhaust the memory available of a program completely
-  and make it crash, or slow it down significantly. (Denial of Service)
-
-Both of these scenarios are considered serious security issues in a real-world
-web server context.
-
-When using `Buffer.from(req.body.string)` instead, passing a number will always
-throw an exception instead, giving a controlled behavior that can always be
-handled by the program.
-
-### <!--ecosystem-usage-->The `Buffer()` constructor has been deprecated for a while. Is this really an issue?
-
-Surveys of code in the `npm` ecosystem have shown that the `Buffer()` constructor is still
-widely used. This includes new code, and overall usage of such code has actually been
-_increasing_.
diff --git a/pages/en/docs/guides/domain-postmortem.md b/pages/en/docs/guides/domain-postmortem.md
deleted file mode 100644
index a73a426ccdb46..0000000000000
--- a/pages/en/docs/guides/domain-postmortem.md
+++ /dev/null
@@ -1,466 +0,0 @@
----
-title: Domain Module Postmortem
-layout: docs.hbs
----
-
-# Domain Module Postmortem
-
-## Usability Issues
-
-### Implicit Behavior
-
-It's possible for a developer to create a new domain and then simply run
-`domain.enter()`. Which then acts as a catch-all for any exception in the
-future that couldn't be observed by the thrower. Allowing a module author to
-intercept the exceptions of unrelated code in a different module. Preventing
-the originator of the code from knowing about its own exceptions.
-
-Here's an example of how one indirectly linked modules can affect another:
-
-```js
-// module a.js
-const b = require('./b');
-const c = require('./c');
-
-// module b.js
-const d = require('domain').create();
-d.on('error', () => {
-  /* silence everything */
-});
-d.enter();
-
-// module c.js
-const dep = require('some-dep');
-dep.method(); // Uh-oh! This method doesn't actually exist.
-```
-
-Since module `b` enters the domain but never exits any uncaught exception will
-be swallowed. Leaving module `c` in the dark as to why it didn't run the entire
-script. Leaving a potentially partially populated `module.exports`. Doing this
-is not the same as listening for `'uncaughtException'`. As the latter is
-explicitly meant to globally catch errors. The other issue is that domains are
-processed prior to any `'uncaughtException'` handlers, and prevent them from
-running.
-
-Another issue is that domains route errors automatically if no `'error'`
-handler was set on the event emitter. There is no opt-in mechanism for this,
-and automatically propagates across the entire asynchronous chain. This may
-seem useful at first, but once asynchronous calls are two or more modules deep
-and one of them doesn't include an error handler the creator of the domain will
-suddenly be catching unexpected exceptions, and the thrower's exception will go
-unnoticed by the author.
-
-The following is a simple example of how a missing `'error'` handler allows
-the active domain to hijack the error:
-
-```js
-const domain = require('domain');
-const net = require('net');
-const d = domain.create();
-d.on('error', err => console.error(err.message));
-
-d.run(() =>
-  net
-    .createServer(c => {
-      c.end();
-      c.write('bye');
-    })
-    .listen(8000)
-);
-```
-
-Even manually removing the connection via `d.remove(c)` does not prevent the
-connection's error from being automatically intercepted.
-
-Failures that plagues both error routing and exception handling are the
-inconsistencies in how errors are bubbled. The following is an example of how
-nested domains will and won't bubble the exception based on when they happen:
-
-```js
-const domain = require('domain');
-const net = require('net');
-const d = domain.create();
-d.on('error', () => console.error('d intercepted an error'));
-
-d.run(() => {
-  const server = net
-    .createServer(c => {
-      const e = domain.create(); // No 'error' handler being set.
-      e.run(() => {
-        // This will not be caught by d's error handler.
-        setImmediate(() => {
-          throw new Error('thrown from setImmediate');
-        });
-        // Though this one will bubble to d's error handler.
-        throw new Error('immediately thrown');
-      });
-    })
-    .listen(8080);
-});
-```
-
-It may be expected that nested domains always remain nested, and will always
-propagate the exception up the domain stack. Or that exceptions will never
-automatically bubble. Unfortunately both these situations occur, leading to
-potentially confusing behavior that may even be prone to difficult to debug
-timing conflicts.
-
-### API Gaps
-
-While APIs based on using `EventEmitter` can use `bind()` and errback style
-callbacks can use `intercept()`, alternative APIs that implicitly bind to the
-active domain must be executed inside of `run()`. Meaning if module authors
-wanted to support domains using a mechanism alternative to those mentioned they
-must manually implement domain support themselves. Instead of being able to
-leverage the implicit mechanisms already in place.
-
-### Error Propagation
-
-Propagating errors across nested domains is not straight forward, if even
-possible. Existing documentation shows a simple example of how to `close()` an
-`http` server if there is an error in the request handler. What it does not
-explain is how to close the server if the request handler creates another
-domain instance for another async request. Using the following as a simple
-example of the failing of error propagation:
-
-```js
-const d1 = domain.create();
-d1.foo = true; // custom member to make more visible in console
-d1.on('error', er => {
-  /* handle error */
-});
-
-d1.run(() =>
-  setTimeout(() => {
-    const d2 = domain.create();
-    d2.bar = 43;
-    d2.on('error', er => console.error(er.message, domain._stack));
-    d2.run(() => {
-      setTimeout(() => {
-        setTimeout(() => {
-          throw new Error('outer');
-        });
-        throw new Error('inner');
-      });
-    });
-  })
-);
-```
-
-Even in the case that the domain instances are being used for local storage so
-access to resources are made available there is still no way to allow the error
-to continue propagating from `d2` back to `d1`. Quick inspection may tell us
-that simply throwing from `d2`'s domain `'error'` handler would allow `d1` to
-then catch the exception and execute its own error handler. Though that is not
-the case. Upon inspection of `domain._stack` you'll see that the stack only
-contains `d2`.
-
-This may be considered a failing of the API, but even if it did operate in this
-way there is still the issue of transmitting the fact that a branch in the
-asynchronous execution has failed, and that all further operations in that
-branch must cease. In the example of the http request handler, if we fire off
-several asynchronous requests and each one then `write()`'s data back to the
-client many more errors will arise from attempting to `write()` to a closed
-handle. More on this in _Resource Cleanup on Exception_.
-
-### Resource Cleanup on Exception
-
-The following script contains a more complex example of properly cleaning up
-in a small resource dependency tree in the case that an exception occurs in a
-given connection or any of its dependencies. Breaking down the script into its
-basic operations:
-
-```js
-'use strict';
-
-const domain = require('domain');
-const EventEmitter = require('events');
-const fs = require('fs');
-const net = require('net');
-const print = process._rawDebug;
-
-const pipeList = [];
-const FILENAME = '/tmp/tmp.tmp';
-const PIPENAME = '/tmp/node-domain-example-';
-const FILESIZE = 1024;
-let uid = 0;
-
-// Setting up temporary resources
-const buf = Buffer.alloc(FILESIZE);
-for (let i = 0; i < buf.length; i++) buf[i] = ((Math.random() * 1e3) % 78) + 48; // Basic ASCII
-fs.writeFileSync(FILENAME, buf);
-
-class ConnectionResource extends EventEmitter {
-  constructor(c) {
-    super();
-
-    this._connection = c;
-    this._alive = true;
-    this._domain = domain.create();
-    this._id = Math.random().toString(32).substr(2).substr(0, 8) + ++uid;
-
-    this._domain.add(c);
-    this._domain.on('error', () => {
-      this._alive = false;
-    });
-  }
-
-  end(chunk) {
-    this._alive = false;
-    this._connection.end(chunk);
-    this.emit('end');
-  }
-
-  isAlive() {
-    return this._alive;
-  }
-
-  id() {
-    return this._id;
-  }
-
-  write(chunk) {
-    this.emit('data', chunk);
-    return this._connection.write(chunk);
-  }
-}
-
-// Example begin
-net
-  .createServer(c => {
-    const cr = new ConnectionResource(c);
-
-    const d1 = domain.create();
-    fs.open(
-      FILENAME,
-      'r',
-      d1.intercept(fd => {
-        streamInParts(fd, cr, 0);
-      })
-    );
-
-    pipeData(cr);
-
-    c.on('close', () => cr.end());
-  })
-  .listen(8080);
-
-function streamInParts(fd, cr, pos) {
-  const d2 = domain.create();
-  const alive = true;
-  d2.on('error', er => {
-    print('d2 error:', er.message);
-    cr.end();
-  });
-  fs.read(
-    fd,
-    Buffer.alloc(10),
-    0,
-    10,
-    pos,
-    d2.intercept((bRead, buf) => {
-      if (!cr.isAlive()) {
-        return fs.close(fd);
-      }
-      if (cr._connection.bytesWritten < FILESIZE) {
-        // Documentation says callback is optional, but doesn't mention that if
-        // the write fails an exception will be thrown.
-        const goodtogo = cr.write(buf);
-        if (goodtogo) {
-          setTimeout(() => streamInParts(fd, cr, pos + bRead), 1000);
-        } else {
-          cr._connection.once('drain', () =>
-            streamInParts(fd, cr, pos + bRead)
-          );
-        }
-        return;
-      }
-      cr.end(buf);
-      fs.close(fd);
-    })
-  );
-}
-
-function pipeData(cr) {
-  const pname = PIPENAME + cr.id();
-  const ps = net.createServer();
-  const d3 = domain.create();
-  const connectionList = [];
-  d3.on('error', er => {
-    print('d3 error:', er.message);
-    cr.end();
-  });
-  d3.add(ps);
-  ps.on('connection', conn => {
-    connectionList.push(conn);
-    conn.on('data', () => {}); // don't care about incoming data.
-    conn.on('close', () => {
-      connectionList.splice(connectionList.indexOf(conn), 1);
-    });
-  });
-  cr.on('data', chunk => {
-    for (let i = 0; i < connectionList.length; i++) {
-      connectionList[i].write(chunk);
-    }
-  });
-  cr.on('end', () => {
-    for (let i = 0; i < connectionList.length; i++) {
-      connectionList[i].end();
-    }
-    ps.close();
-  });
-  pipeList.push(pname);
-  ps.listen(pname);
-}
-
-process.on('SIGINT', () => process.exit());
-process.on('exit', () => {
-  try {
-    for (let i = 0; i < pipeList.length; i++) {
-      fs.unlinkSync(pipeList[i]);
-    }
-    fs.unlinkSync(FILENAME);
-  } catch (e) {}
-});
-```
-
-- When a new connection happens, concurrently:
-  - Open a file on the file system
-  - Open Pipe to unique socket
-- Read a chunk of the file asynchronously
-- Write chunk to both the TCP connection and any listening sockets
-- If any of these resources error, notify all other attached resources that
-  they need to clean up and shutdown
-
-As we can see from this example a lot more must be done to properly clean up
-resources when something fails than what can be done strictly through the
-domain API. All that domains offer is an exception aggregation mechanism. Even
-the potentially useful ability to propagate data with the domain is easily
-countered, in this example, by passing the needed resources as a function
-argument.
-
-One problem domains perpetuated was the supposed simplicity of being able to
-continue execution, contrary to what the documentation stated, of the
-application despite an unexpected exception. This example demonstrates the
-fallacy behind that idea.
-
-Attempting proper resource cleanup on unexpected exception becomes more complex
-as the application itself grows in complexity. This example only has 3 basic
-resources in play, and all of them with a clear dependency path. If an
-application uses something like shared resources or resource reuse the ability
-to cleanup, and properly test that cleanup has been done, grows greatly.
-
-In the end, in terms of handling errors, domains aren't much more than a
-glorified `'uncaughtException'` handler. Except with more implicit and
-unobservable behavior by third-parties.
-
-### Resource Propagation
-
-Another use case for domains was to use it to propagate data along asynchronous
-data paths. One problematic point is the ambiguity of when to expect the
-correct domain when there are multiple in the stack (which must be assumed if
-the async stack works with other modules). Also the conflict between being
-able to depend on a domain for error handling while also having it available to
-retrieve the necessary data.
-
-The following is a involved example demonstrating the failing using domains to
-propagate data along asynchronous stacks:
-
-```js
-const domain = require('domain');
-const net = require('net');
-
-const server = net
-  .createServer(c => {
-    // Use a domain to propagate data across events within the
-    // connection so that we don't have to pass arguments
-    // everywhere.
-    const d = domain.create();
-    d.data = { connection: c };
-    d.add(c);
-    // Mock class that does some useless async data transformation
-    // for demonstration purposes.
-    const ds = new DataStream(dataTransformed);
-    c.on('data', chunk => ds.data(chunk));
-  })
-  .listen(8080, () => console.log('listening on 8080'));
-
-function dataTransformed(chunk) {
-  // FAIL! Because the DataStream instance also created a
-  // domain we have now lost the active domain we had
-  // hoped to use.
-  domain.active.data.connection.write(chunk);
-}
-
-class DataStream {
-  constructor(cb) {
-    this.cb = cb;
-    // DataStream wants to use domains for data propagation too!
-    // Unfortunately this will conflict with any domain that
-    // already exists.
-    this.domain = domain.create();
-    this.domain.data = { inst: this };
-  }
-
-  data(chunk) {
-    // This code is self contained, but pretend it's a complex
-    // operation that crosses at least one other module. So
-    // passing along "this", etc., is not easy.
-    this.domain.run(() => {
-      // Simulate an async operation that does the data transform.
-      setImmediate(() => {
-        for (let i = 0; i < chunk.length; i++)
-          chunk[i] = ((chunk[i] + Math.random() * 100) % 96) + 33;
-        // Grab the instance from the active domain and use that
-        // to call the user's callback.
-        const self = domain.active.data.inst;
-        self.cb(chunk);
-      });
-    });
-  }
-}
-```
-
-The above shows that it is difficult to have more than one asynchronous API
-attempt to use domains to propagate data. This example could possibly be fixed
-by assigning `parent: domain.active` in the `DataStream` constructor. Then
-restoring it via `domain.active = domain.active.data.parent` just before the
-user's callback is called. Also the instantiation of `DataStream` in the
-`'connection'` callback must be run inside `d.run()`, instead of simply using
-`d.add(c)`, otherwise there will be no active domain.
-
-In short, for this to have a prayer of a chance usage would need to strictly
-adhere to a set of guidelines that would be difficult to enforce or test.
-
-## Performance Issues
-
-A significant deterrent from using domains is the overhead. Using node's
-built-in http benchmark, `http_simple.js`, without domains it can handle over
-22,000 requests/second. Whereas if it's run with `NODE_USE_DOMAINS=1` that
-number drops down to under 17,000 requests/second. In this case there is only
-a single global domain. If we edit the benchmark so the http request callback
-creates a new domain instance performance drops further to 15,000
-requests/second.
-
-While this probably wouldn't affect a server only serving a few hundred or even
-a thousand requests per second, the amount of overhead is directly proportional
-to the number of asynchronous requests made. So if a single connection needs to
-connect to several other services all of those will contribute to the overall
-latency of delivering the final product to the client.
-
-Using `AsyncWrap` and tracking the number of times
-`init`/`pre`/`post`/`destroy` are called in the mentioned benchmark we find
-that the sum of all events called is over 170,000 times per second. This means
-even adding 1 microsecond overhead per call for any type of setup or tear down
-will result in a 17% performance loss. Granted, this is for the optimized
-scenario of the benchmark, but I believe this demonstrates the necessity for a
-mechanism such as domain to be as cheap to run as possible.
-
-## Looking Ahead
-
-The domain module has been soft deprecated since Dec 2014, but has not yet been
-removed because node offers no alternative functionality at the moment. As of
-this writing there is ongoing work building out the `AsyncWrap` API and a
-proposal for Zones being prepared for the TC39. At such time there is suitable
-functionality to replace domains it will undergo the full deprecation cycle and
-eventually be removed from core.
diff --git a/pages/en/docs/guides/getting-started-guide.md b/pages/en/docs/guides/getting-started-guide.md
deleted file mode 100644
index ee0ca007fdfa3..0000000000000
--- a/pages/en/docs/guides/getting-started-guide.md
+++ /dev/null
@@ -1,32 +0,0 @@
----
-title: Getting Started Guide
-layout: docs.hbs
----
-
-# How do I start with Node.js after I installed it?
-
-Once we have installed Node.js, let's build our first web server.
-Create a file named `app.js` containing the following contents:
-
-```javascript
-const http = require('http');
-
-const hostname = '127.0.0.1';
-const port = 3000;
-
-const server = http.createServer((req, res) => {
-  res.statusCode = 200;
-  res.setHeader('Content-Type', 'text/plain');
-  res.end('Hello World');
-});
-
-server.listen(port, hostname, () => {
-  console.log(`Server running at http://${hostname}:${port}/`);
-});
-```
-
-Now, run your web server using `node app.js`. Visit `http://localhost:3000` and
-you will see a message saying "Hello World".
-
-Refer to the [Introduction to Node.js](https://nodejs.dev/en/learn/) for a more
-comprehensive guide to getting started with Node.js.
diff --git a/pages/en/docs/guides/index.md b/pages/en/docs/guides/index.md
index 3ec6e16d74d6e..acb432615acef 100644
--- a/pages/en/docs/guides/index.md
+++ b/pages/en/docs/guides/index.md
@@ -3,31 +3,25 @@ title: Guides
 layout: docs.hbs
 ---
 
-# Guides
+# Node.js Guides
 
 ## General
 
-- [Getting Started Guide](/docs/guides/getting-started-guide/)
 - [Debugging - Getting Started](/docs/guides/debugging-getting-started/)
 - [Easy profiling for Node.js Applications](/docs/guides/simple-profiling/)
 - [Diagnostics - Flame Graphs](/docs/guides/diagnostics-flamegraph/)
-- [Dockerizing a Node.js web app](/docs/guides/nodejs-docker-webapp/)
-- [Migrating to safe Buffer constructors](/docs/guides/buffer-constructor-deprecation/)
 - [Diagnostics - User Journey](/docs/guides/diagnostics/)
 - [Security Best Practices](/docs/guides/security/)
 
 ## Node.js core concepts
 
-- [Overview of Blocking vs Non-Blocking](/docs/guides/blocking-vs-non-blocking/)
 - [The Node.js Event Loop, Timers, and `process.nextTick()`](/docs/guides/event-loop-timers-and-nexttick/)
 - [Don't Block the Event Loop (or the Worker Pool)](/docs/guides/dont-block-the-event-loop/)
-- [Timers in Node.js](/docs/guides/timers-in-node/)
 
 ## Module-related guides
 
 - [Anatomy of an HTTP Transaction](/docs/guides/anatomy-of-an-http-transaction/)
 - [Working with Different Filesystems](/docs/guides/working-with-different-filesystems/)
 - [Backpressuring in Streams](/docs/guides/backpressuring-in-streams/)
-- [Domain Module Postmortem](/docs/guides/domain-postmortem/)
 - [How to publish N-API package](/docs/guides/publishing-napi-modules/)
 - [ABI Stability](/docs/guides/abi-stability/)
diff --git a/pages/en/docs/guides/nodejs-docker-webapp.md b/pages/en/docs/guides/nodejs-docker-webapp.md
deleted file mode 100644
index 86aeeee95673f..0000000000000
--- a/pages/en/docs/guides/nodejs-docker-webapp.md
+++ /dev/null
@@ -1,289 +0,0 @@
----
-title: Dockerizing a Node.js web app
-layout: docs.hbs
----
-
-# Dockerizing a Node.js web app
-
-The goal of this example is to show you how to get a Node.js application into a
-Docker container. The guide is intended for development, and _not_ for a
-production deployment. The guide also assumes you have a working [Docker
-installation](https://docs.docker.com/engine/installation/) and a basic
-understanding of how a Node.js application is structured.
-
-In the first part of this guide we will create a simple web application in
-Node.js, then we will build a Docker image for that application, and lastly we
-will instantiate a container from that image.
-
-Docker allows you to package an application with its environment and all of its dependencies into a
-"box", called a container. Usually, a container consists of an application running in a stripped-to-basics version of a Linux operating system. An image is the blueprint for a container, a container is a running instance of an image.
-
-## Create the Node.js app
-
-First, create a new directory where all the files would live. In this directory
-create a `package.json` file that describes your app and its dependencies:
-
-```json
-{
-  "name": "docker_web_app",
-  "version": "1.0.0",
-  "description": "Node.js on Docker",
-  "author": "First Last <first.last@example.com>",
-  "main": "server.js",
-  "scripts": {
-    "start": "node server.js"
-  },
-  "dependencies": {
-    "express": "^4.18.2"
-  }
-}
-```
-
-With your new `package.json` file, run `npm install`. If you are using `npm`
-version 5 or later, this will generate a `package-lock.json` file which will be copied
-to your Docker image.
-
-Then, create a `server.js` file that defines a web app using the
-[Express.js](https://expressjs.com/) framework:
-
-```javascript
-'use strict';
-
-const express = require('express');
-
-// Constants
-const PORT = 8080;
-const HOST = '0.0.0.0';
-
-// App
-const app = express();
-app.get('/', (req, res) => {
-  res.send('Hello World');
-});
-
-app.listen(PORT, HOST, () => {
-  console.log(`Running on http://${HOST}:${PORT}`);
-});
-```
-
-In the next steps, we'll look at how you can run this app inside a Docker
-container using the official Docker image. First, you'll need to build a Docker
-image of your app.
-
-## Creating a Dockerfile
-
-Create an empty file called `Dockerfile`:
-
-```bash
-touch Dockerfile
-```
-
-Open the `Dockerfile` in your favorite text editor
-
-The first thing we need to do is define from what image we want to build from.
-Here we will use the latest LTS (long term support) version `18` of `node`
-available from the [Docker Hub](https://hub.docker.com/_/node):
-
-```dockerfile
-FROM node:18
-```
-
-Next we create a directory to hold the application code inside the image, this
-will be the working directory for your application:
-
-```dockerfile
-# Create app directory
-WORKDIR /usr/src/app
-```
-
-This image comes with Node.js and NPM already installed so the next thing we
-need to do is to install your app dependencies using the `npm` binary. Please
-note that if you are using `npm` version 4 or earlier a `package-lock.json`
-file will _not_ be generated.
-
-```dockerfile
-# Install app dependencies
-# A wildcard is used to ensure both package.json AND package-lock.json are copied
-# where available (npm@5+)
-COPY package*.json ./
-
-RUN npm install
-# If you are building your code for production
-# RUN npm ci --omit=dev
-```
-
-Note that, rather than copying the entire working directory, we are only copying
-the `package.json` file. This allows us to take advantage of cached Docker
-layers. bitJudo has a good explanation of this
-[here](http://bitjudo.com/blog/2014/03/13/building-efficient-dockerfiles-node-dot-js/).
-Furthermore, the `npm ci` command, specified in the comments, helps provide faster, reliable, reproducible builds for production environments.
-You can read more about this [here](https://blog.npmjs.org/post/171556855892/introducing-npm-ci-for-faster-more-reliable).
-
-To bundle your app's source code inside the Docker image, use the `COPY`
-instruction:
-
-```dockerfile
-# Bundle app source
-COPY . .
-```
-
-Your app binds to port `8080` so you'll use the `EXPOSE` instruction to have it
-mapped by the `docker` daemon:
-
-```dockerfile
-EXPOSE 8080
-```
-
-Last but not least, define the command to run your app using `CMD` which defines
-your runtime. Here we will use `node server.js` to start your server:
-
-```dockerfile
-CMD [ "node", "server.js" ]
-```
-
-Your `Dockerfile` should now look like this:
-
-```dockerfile
-FROM node:18
-
-# Create app directory
-WORKDIR /usr/src/app
-
-# Install app dependencies
-# A wildcard is used to ensure both package.json AND package-lock.json are copied
-# where available (npm@5+)
-COPY package*.json ./
-
-RUN npm install
-# If you are building your code for production
-# RUN npm ci --omit=dev
-
-# Bundle app source
-COPY . .
-
-EXPOSE 8080
-CMD [ "node", "server.js" ]
-```
-
-## .dockerignore file
-
-Create a `.dockerignore` file in the same directory as your `Dockerfile`
-with following content:
-
-```
-node_modules
-npm-debug.log
-```
-
-This will prevent your local modules and debug logs from being copied onto your
-Docker image and possibly overwriting modules installed within your image.
-
-## Building your image
-
-Go to the directory that has your `Dockerfile` and run the following command to
-build the Docker image. The `-t` flag lets you tag your image so it's easier to
-find later using the `docker images` command:
-
-```bash
-docker build . -t <your username>/node-web-app
-```
-
-Your image will now be listed by Docker:
-
-```bash
-$ docker images
-
-# Example
-REPOSITORY                      TAG        ID              CREATED
-node                            18         78b037dbb659    2 weeks ago
-<your username>/node-web-app    latest     d64d3505b0d2    1 minute ago
-```
-
-## Run the image
-
-Running your image with `-d` runs the container in detached mode, leaving the
-container running in the background. The `-p` flag redirects a public port to a
-private port inside the container. Run the image you previously built:
-
-```bash
-docker run -p 49160:8080 -d <your username>/node-web-app
-```
-
-Print the output of your app:
-
-```bash
-# Get container ID
-$ docker ps
-
-# Print app output
-$ docker logs <container id>
-
-# Example
-Running on http://localhost:8080
-```
-
-If you need to go inside the container you can use the `exec` command:
-
-```bash
-# Enter the container
-$ docker exec -it <container id> /bin/bash
-```
-
-## Test
-
-To test your app, get the port of your app that Docker mapped:
-
-```bash
-$ docker ps
-
-# Example
-ID            IMAGE                                COMMAND    ...   PORTS
-ecce33b30ebf  <your username>/node-web-app:latest  npm start  ...   49160->8080
-```
-
-In the example above, Docker mapped the `8080` port inside of the container to
-the port `49160` on your machine.
-
-Now you can call your app using `curl` (install if needed via: `sudo apt-get
-install curl`):
-
-```bash
-$ curl -i localhost:49160
-
-HTTP/1.1 200 OK
-X-Powered-By: Express
-Content-Type: text/html; charset=utf-8
-Content-Length: 12
-ETag: W/"c-M6tWOb/Y57lesdjQuHeB1P/qTV0"
-Date: Mon, 13 Nov 2017 20:53:59 GMT
-Connection: keep-alive
-
-Hello world
-```
-
-## Shut down the image
-
-In order to shut down the app we started, we run the `kill` command. This uses
-the container's ID, which in this example was `ecce33b30ebf`.
-
-```bash
-# Kill our running container
-$ docker kill <container id>
-<container id>
-
-# Confirm that the app has stopped
-$ curl -i localhost:49160
-curl: (7) Failed to connect to localhost port 49160: Connection refused
-```
-
-We hope this tutorial helped you get up and running a simple Node.js application
-on Docker.
-
-You can find more information about Docker and Node.js on Docker in the
-following places:
-
-- [Official Node.js Docker Image](https://hub.docker.com/_/node/)
-- [Node.js Docker Best Practices Guide](https://github.com/nodejs/docker-node/blob/master/docs/BestPractices.md)
-- [Official Docker documentation](https://docs.docker.com/get-started/nodejs/build-images/)
-- [Docker Tag on Stack Overflow](https://stackoverflow.com/questions/tagged/docker)
-- [Docker Subreddit](https://reddit.com/r/docker)
diff --git a/pages/en/docs/guides/timers-in-node.md b/pages/en/docs/guides/timers-in-node.md
deleted file mode 100644
index 9c4df88492611..0000000000000
--- a/pages/en/docs/guides/timers-in-node.md
+++ /dev/null
@@ -1,194 +0,0 @@
----
-title: Timers in Node.js
-layout: docs.hbs
----
-
-# Timers in Node.js and beyond
-
-The Timers module in Node.js contains functions that execute code after a set
-period of time. Timers do not need to be imported via `require()`, since
-all the methods are available globally to emulate the browser JavaScript API.
-To fully understand when timer functions will be executed, it's a good idea to
-read up on the Node.js
-[Event Loop](/docs/guides/event-loop-timers-and-nexttick/).
-
-## Controlling the Time Continuum with Node.js
-
-The Node.js API provides several ways of scheduling code to execute at
-some point after the present moment. The functions below may seem familiar,
-since they are available in most browsers, but Node.js actually provides
-its own implementation of these methods. Timers integrate very closely
-with the system, and despite the fact that the API mirrors the browser
-API, there are some differences in implementation.
-
-### "When I say so" Execution ~ _`setTimeout()`_
-
-`setTimeout()` can be used to schedule code execution after a designated
-amount of milliseconds. This function is similar to
-[`window.setTimeout()`](https://developer.mozilla.org/en-US/docs/Web/API/WindowTimers/setTimeout)
-from the browser JavaScript API, however a string of code cannot be passed
-to be executed.
-
-`setTimeout()` accepts a function to execute as its first argument and the
-millisecond delay defined as a number as the second argument. Additional
-arguments may also be included and these will be passed on to the function. Here
-is an example of that:
-
-```js
-function myFunc(arg) {
-  console.log(`arg was => ${arg}`);
-}
-
-setTimeout(myFunc, 1500, 'funky');
-```
-
-The above function `myFunc()` will execute as close to 1500
-milliseconds (or 1.5 seconds) as possible due to the call of `setTimeout()`.
-
-The timeout interval that is set cannot be relied upon to execute after
-that _exact_ number of milliseconds. This is because other executing code that
-blocks or holds onto the event loop will push the execution of the timeout
-back. The _only_ guarantee is that the timeout will not execute _sooner_ than
-the declared timeout interval.
-
-`setTimeout()` returns a `Timeout` object that can be used to reference the
-timeout that was set. This returned object can be used to cancel the timeout (
-see `clearTimeout()` below) as well as change the execution behavior (see
-`unref()` below).
-
-### "Right after this" Execution ~ _`setImmediate()`_
-
-`setImmediate()` will execute code at the end of the current event loop cycle.
-This code will execute _after_ any I/O operations in the current event loop and
-_before_ any timers scheduled for the next event loop. This code execution
-could be thought of as happening "right after this", meaning any code following
-the `setImmediate()` function call will execute before the `setImmediate()`
-function argument.
-
-The first argument to `setImmediate()` will be the function to execute. Any
-subsequent arguments will be passed to the function when it is executed.
-Here's an example:
-
-```js
-console.log('before immediate');
-
-setImmediate(arg => {
-  console.log(`executing immediate: ${arg}`);
-}, 'so immediate');
-
-console.log('after immediate');
-```
-
-The above function passed to `setImmediate()` will execute after all runnable
-code has executed, and the console output will be:
-
-```
-before immediate
-after immediate
-executing immediate: so immediate
-```
-
-`setImmediate()` returns an `Immediate` object, which can be used to cancel
-the scheduled immediate (see `clearImmediate()` below).
-
-> Don't get `setImmediate()` confused with `process.nextTick()`. There are
-> some major ways they differ. The first is that `process.nextTick()` will run
-> _before_ any `Immediate`s that are set as well as before any scheduled I/O.
-> The second is that `process.nextTick()` is non-clearable, meaning once
-> code has been scheduled to execute with `process.nextTick()`, the execution
-> cannot be stopped, just like with a normal function. Refer to [this guide](/docs/guides/event-loop-timers-and-nexttick/#process-nexttick)
-> to better understand the operation of `process.nextTick()`.
-
-### "Infinite Loop" Execution ~ _`setInterval()`_
-
-If there is a block of code that should execute multiple times, `setInterval()`
-can be used to execute that code. `setInterval()` takes a function
-argument that will run an infinite number of times with a given millisecond
-delay as the second argument. Just like `setTimeout()`, additional arguments
-can be added beyond the delay, and these will be passed on to the function call.
-Also like `setTimeout()`, the delay cannot be guaranteed because of operations
-that may hold on to the event loop, and therefore should be treated as an
-approximate delay. See the below example:
-
-```js
-function intervalFunc() {
-  console.log('Cant stop me now!');
-}
-
-setInterval(intervalFunc, 1500);
-```
-
-In the above example, `intervalFunc()` will execute about every 1500
-milliseconds, or 1.5 seconds, until it is stopped (see below).
-
-Just like `setTimeout()`, `setInterval()` also returns a `Timeout` object which
-can be used to reference and modify the interval that was set.
-
-## Clearing the Future
-
-What can be done if a `Timeout` or `Immediate` object needs to be cancelled?
-`setTimeout()`, `setImmediate()`, and `setInterval()` return a timer object
-that can be used to reference the set `Timeout` or `Immediate` object.
-By passing said object into the respective `clear` function, execution of
-that object will be halted completely. The respective functions are
-`clearTimeout()`, `clearImmediate()`, and `clearInterval()`. See the example
-below for an example of each:
-
-```js
-const timeoutObj = setTimeout(() => {
-  console.log('timeout beyond time');
-}, 1500);
-
-const immediateObj = setImmediate(() => {
-  console.log('immediately executing immediate');
-});
-
-const intervalObj = setInterval(() => {
-  console.log('interviewing the interval');
-}, 500);
-
-clearTimeout(timeoutObj);
-clearImmediate(immediateObj);
-clearInterval(intervalObj);
-```
-
-## Leaving Timeouts Behind
-
-Remember that `Timeout` objects are returned by `setTimeout` and `setInterval`.
-The `Timeout` object provides two functions intended to augment `Timeout`
-behavior with `unref()` and `ref()`. If there is a `Timeout` object scheduled
-using a `set` function, `unref()` can be called on that object. This will change
-the behavior slightly, and not call the `Timeout` object _if it is the last
-code to execute_. The `Timeout` object will not keep the process alive, waiting
-to execute.
-
-In similar fashion, a `Timeout` object that has had `unref()` called on it
-can remove that behavior by calling `ref()` on that same `Timeout` object,
-which will then ensure its execution. Be aware, however, that this does
-not _exactly_ restore the initial behavior for performance reasons. See
-below for examples of both:
-
-```js
-const timerObj = setTimeout(() => {
-  console.log('will i run?');
-});
-
-// if left alone, this statement will keep the above
-// timeout from running, since the timeout will be the only
-// thing keeping the program from exiting
-timerObj.unref();
-
-// we can bring it back to life by calling ref() inside
-// an immediate
-setImmediate(() => {
-  timerObj.ref();
-});
-```
-
-## Further Down the Event Loop
-
-There's much more to the Event Loop and Timers than this guide
-has covered. To learn more about the internals of the Node.js
-Event Loop and how Timers operate during execution, check out
-this Node.js guide: [The Node.js Event Loop, Timers, and
-process.nextTick()](/docs/guides/event-loop-timers-and-nexttick/).
diff --git a/pages/en/learn/asynchronous-work/asynchronous-flow-control.md b/pages/en/learn/asynchronous-work/asynchronous-flow-control.md
new file mode 100644
index 0000000000000..29780adb4bf36
--- /dev/null
+++ b/pages/en/learn/asynchronous-work/asynchronous-flow-control.md
@@ -0,0 +1,271 @@
+---
+title: Asynchronous flow control
+layout: learn.hbs
+authors: aug2uag, ovflowd
+---
+
+# Asynchronous flow control
+
+> The material in this post is heavily inspired by [Mixu's Node.js Book](http://book.mixu.net/node/ch7.html).
+
+At its core, JavaScript is designed to be non-blocking on the "main" thread, this is where views are rendered. You can imagine the importance of this in the browser. When the main thread becomes blocked it results in the infamous "freezing" that end users dread, and no other events can be dispatched resulting in the loss of data acquisition, for example.
+
+This creates some unique constraints that only a functional style of programming can cure. This is where callbacks come in to the picture.
+
+However, callbacks can become challenging to handle in more complicated procedures. This often results in "callback hell" where multiple nested functions with callbacks make the code more challenging to read, debug, organize, etc.
+
+```js
+async1(function (input, result1) {
+  async2(function (result2) {
+    async3(function (result3) {
+      async4(function (result4) {
+        async5(function (output) {
+          // do something with output
+        });
+      });
+    });
+  });
+});
+```
+
+Of course, in real life there would most likely be additional lines of code to handle `result1`, `result2`, etc., thus, the length and complexity of this issue usually results in code that looks much more messy than the example above.
+
+**This is where _functions_ come in to great use. More complex operations are made up of many functions:**
+
+1. initiator style / input
+2. middleware
+3. terminator
+
+**The "initiator style / input" is the first function in the sequence. This function will accept the original input, if any, for the operation. The operation is an executable series of functions, and the original input will primarily be:**
+
+1. variables in a global environment
+2. direct invocation with or without arguments
+3. values obtained by file system or network requests
+
+Network requests can be incoming requests initiated by a foreign network, by another application on the same network, or by the app itself on the same or foreign network.
+
+A middleware function will return another function, and a terminator function will invoke the callback. The following illustrates the flow to network or file system requests. Here the latency is 0 because all these values are available in memory.
+
+```js
+function final(someInput, callback) {
+  callback(`${someInput} and terminated by executing callback `);
+}
+
+function middleware(someInput, callback) {
+  return final(`${someInput} touched by middleware `, callback);
+}
+
+function initiate() {
+  const someInput = 'hello this is a function ';
+  middleware(someInput, function (result) {
+    console.log(result);
+    // requires callback to `return` result
+  });
+}
+
+initiate();
+```
+
+## State management
+
+Functions may or may not be state dependent. State dependency arises when the input or other variable of a function relies on an outside function.
+
+**In this way there are two primary strategies for state management:**
+
+1. passing in variables directly to a function, and
+2. acquiring a variable value from a cache, session, file, database, network, or other outside source.
+
+Note, I did not mention global variable. Managing state with global variables is often a sloppy anti-pattern that makes it difficult or impossible to guarantee state. Global variables in complex programs should be avoided when possible.
+
+## Control flow
+
+If an object is available in memory, iteration is possible, and there will not be a change to control flow:
+
+```js
+function getSong() {
+  let _song = '';
+  let i = 100;
+  for (i; i > 0; i -= 1) {
+    _song += `${i} beers on the wall, you take one down and pass it around, ${
+      i - 1
+    } bottles of beer on the wall\n`;
+    if (i === 1) {
+      _song += "Hey let's get some more beer";
+    }
+  }
+
+  return _song;
+}
+
+function singSong(_song) {
+  if (!_song) throw new Error("song is '' empty, FEED ME A SONG!");
+  console.log(_song);
+}
+
+const song = getSong();
+// this will work
+singSong(song);
+```
+
+However, if the data exists outside of memory the iteration will no longer work:
+
+```js
+function getSong() {
+  let _song = '';
+  let i = 100;
+  for (i; i > 0; i -= 1) {
+    /* eslint-disable no-loop-func */
+    setTimeout(function () {
+      _song += `${i} beers on the wall, you take one down and pass it around, ${
+        i - 1
+      } bottles of beer on the wall\n`;
+      if (i === 1) {
+        _song += "Hey let's get some more beer";
+      }
+    }, 0);
+    /* eslint-enable no-loop-func */
+  }
+
+  return _song;
+}
+
+function singSong(_song) {
+  if (!_song) throw new Error("song is '' empty, FEED ME A SONG!");
+  console.log(_song);
+}
+
+const song = getSong('beer');
+// this will not work
+singSong(song);
+// Uncaught Error: song is '' empty, FEED ME A SONG!
+```
+
+Why did this happen? `setTimeout` instructs the CPU to store the instructions elsewhere on the bus, and instructs that the data is scheduled for pickup at a later time. Thousands of CPU cycles pass before the function hits again at the 0 millisecond mark, the CPU fetches the instructions from the bus and executes them. The only problem is that song ('') was returned thousands of cycles prior.
+
+The same situation arises in dealing with file systems and network requests. The main thread simply cannot be blocked for an indeterminate period of time-- therefore, we use callbacks to schedule the execution of code in time in a controlled manner.
+
+You will be able to perform almost all of your operations with the following 3 patterns:
+
+1. **In series:** functions will be executed in a strict sequential order, this one is most similar to `for` loops.
+
+```js
+// operations defined elsewhere and ready to execute
+const operations = [
+  { func: function1, args: args1 },
+  { func: function2, args: args2 },
+  { func: function3, args: args3 },
+];
+
+function executeFunctionWithArgs(operation, callback) {
+  // executes function
+  const { args, func } = operation;
+  func(args, callback);
+}
+
+function serialProcedure(operation) {
+  if (!operation) process.exit(0); // finished
+  executeFunctionWithArgs(operation, function (result) {
+    // continue AFTER callback
+    serialProcedure(operations.shift());
+  });
+}
+
+serialProcedure(operations.shift());
+```
+
+2. **Full parallel:** when ordering is not an issue, such as emailing a list of 1,000,000 email recipients.
+
+```js
+let count = 0;
+let success = 0;
+const failed = [];
+const recipients = [
+  { name: 'Bart', email: 'bart@tld' },
+  { name: 'Marge', email: 'marge@tld' },
+  { name: 'Homer', email: 'homer@tld' },
+  { name: 'Lisa', email: 'lisa@tld' },
+  { name: 'Maggie', email: 'maggie@tld' },
+];
+
+function dispatch(recipient, callback) {
+  // `sendEmail` is a hypothetical SMTP client
+  sendMail(
+    {
+      subject: 'Dinner tonight',
+      message: 'We have lots of cabbage on the plate. You coming?',
+      smtp: recipient.email,
+    },
+    callback
+  );
+}
+
+function final(result) {
+  console.log(`Result: ${result.count} attempts \
+      & ${result.success} succeeded emails`);
+  if (result.failed.length)
+    console.log(`Failed to send to: \
+        \n${result.failed.join('\n')}\n`);
+}
+
+recipients.forEach(function (recipient) {
+  dispatch(recipient, function (err) {
+    if (!err) {
+      success += 1;
+    } else {
+      failed.push(recipient.name);
+    }
+    count += 1;
+
+    if (count === recipients.length) {
+      final({
+        count,
+        success,
+        failed,
+      });
+    }
+  });
+});
+```
+
+3. **Limited parallel:** parallel with limit, such as successfully emailing 1,000,000 recipients from a list of 10E7 users.
+
+```js
+let successCount = 0;
+
+function final() {
+  console.log(`dispatched ${successCount} emails`);
+  console.log('finished');
+}
+
+function dispatch(recipient, callback) {
+  // `sendEmail` is a hypothetical SMTP client
+  sendMail(
+    {
+      subject: 'Dinner tonight',
+      message: 'We have lots of cabbage on the plate. You coming?',
+      smtp: recipient.email,
+    },
+    callback
+  );
+}
+
+function sendOneMillionEmailsOnly() {
+  getListOfTenMillionGreatEmails(function (err, bigList) {
+    if (err) throw err;
+
+    function serial(recipient) {
+      if (!recipient || successCount >= 1000000) return final();
+      dispatch(recipient, function (_err) {
+        if (!_err) successCount += 1;
+        serial(bigList.pop());
+      });
+    }
+
+    serial(bigList.pop());
+  });
+}
+
+sendOneMillionEmailsOnly();
+```
+
+Each has its own use cases, benefits, and issues you can experiment and read about in more detail. Most importantly, remember to modularize your operations and use callbacks! If you feel any doubt, treat everything as if it were middleware!
diff --git a/pages/en/learn/asynchronous-work/discover-javascript-timers.md b/pages/en/learn/asynchronous-work/discover-javascript-timers.md
new file mode 100644
index 0000000000000..2864335f1fc50
--- /dev/null
+++ b/pages/en/learn/asynchronous-work/discover-javascript-timers.md
@@ -0,0 +1,135 @@
+---
+title: Discover JavaScript Timers
+layout: learn.hbs
+authors: flaviocopes, MylesBorins, LaRuaNa, amiller-gh, ahmadawais, ovflowd
+---
+
+# Discover JavaScript Timers
+
+## `setTimeout()`
+
+When writing JavaScript code, you might want to delay the execution of a function.
+
+This is the job of `setTimeout`. You specify a callback function to execute later, and a value expressing how later you want it to run, in milliseconds:
+
+```js
+setTimeout(() => {
+  // runs after 2 seconds
+}, 2000);
+
+setTimeout(() => {
+  // runs after 50 milliseconds
+}, 50);
+```
+
+This syntax defines a new function. You can call whatever other function you want in there, or you can pass an existing function name, and a set of parameters:
+
+```js
+const myFunction = (firstParam, secondParam) => {
+  // do something
+};
+
+// runs after 2 seconds
+setTimeout(myFunction, 2000, firstParam, secondParam);
+```
+
+`setTimeout` returns the timer id. This is generally not used, but you can store this id, and clear it if you want to delete this scheduled function execution:
+
+```js
+const id = setTimeout(() => {
+  // should run after 2 seconds
+}, 2000);
+
+// I changed my mind
+clearTimeout(id);
+```
+
+### Zero delay
+
+If you specify the timeout delay to `0`, the callback function will be executed as soon as possible, but after the current function execution:
+
+```js
+setTimeout(() => {
+  console.log('after ');
+}, 0);
+
+console.log(' before ');
+```
+
+This code will print
+
+```bash
+before
+after
+```
+
+This is especially useful to avoid blocking the CPU on intensive tasks and let other functions be executed while performing a heavy calculation, by queuing functions in the scheduler.
+
+> Some browsers (IE and Edge) implement a `setImmediate()` method that does this same exact functionality, but it's not standard and [unavailable on other browsers](https://caniuse.com/#feat=setimmediate). But it's a standard function in Node.js.
+
+## `setInterval()`
+
+`setInterval` is a function similar to `setTimeout`, with a difference: instead of running the callback function once, it will run it forever, at the specific time interval you specify (in milliseconds):
+
+```js
+setInterval(() => {
+  // runs every 2 seconds
+}, 2000);
+```
+
+The function above runs every 2 seconds unless you tell it to stop, using `clearInterval`, passing it the interval id that `setInterval` returned:
+
+```js
+const id = setInterval(() => {
+  // runs every 2 seconds
+}, 2000);
+
+clearInterval(id);
+```
+
+It's common to call `clearInterval` inside the setInterval callback function, to let it auto-determine if it should run again or stop. For example this code runs something unless App.somethingIWait has the value `arrived`:
+
+```js
+const interval = setInterval(() => {
+  if (App.somethingIWait === 'arrived') {
+    clearInterval(interval);
+  }
+  // otherwise do things
+}, 100);
+```
+
+## Recursive setTimeout
+
+`setInterval` starts a function every n milliseconds, without any consideration about when a function finished its execution.
+
+If a function always takes the same amount of time, it's all fine:
+
+![setInterval working fine](/static/images/learn/javascript-timers/setinterval-ok.png)
+
+Maybe the function takes different execution times, depending on network conditions for example:
+
+![setInterval varying duration](/static/images/learn/javascript-timers/setinterval-varying-duration.png)
+
+And maybe one long execution overlaps the next one:
+
+![setInterval overlapping](/static/images/learn/javascript-timers/setinterval-overlapping.png)
+
+To avoid this, you can schedule a recursive setTimeout to be called when the callback function finishes:
+
+```js
+const myFunction = () => {
+  // do something
+
+  setTimeout(myFunction, 1000);
+};
+
+setTimeout(myFunction, 1000);
+```
+
+to achieve this scenario:
+
+![Recursive setTimeout](/static/images/learn/javascript-timers/recursive-settimeout.png)
+
+`setTimeout` and `setInterval` are available in Node.js, through the [Timers module](https://nodejs.org/api/timers.html).
+
+Node.js also provides `setImmediate()`, which is equivalent to using `setTimeout(() => {}, 0)`, mostly used to work with the Node.js Event Loop.
diff --git a/pages/en/learn/asynchronous-work/javascript-asynchronous-programming-and-callbacks.md b/pages/en/learn/asynchronous-work/javascript-asynchronous-programming-and-callbacks.md
new file mode 100644
index 0000000000000..bd39d33554677
--- /dev/null
+++ b/pages/en/learn/asynchronous-work/javascript-asynchronous-programming-and-callbacks.md
@@ -0,0 +1,134 @@
+---
+title: JavaScript Asynchronous Programming and Callbacks
+layout: learn.hbs
+authors: flaviocopes, MylesBorins, LaRuaNa, amiller-gh, ahmadawais, ovflowd
+---
+
+# JavaScript Asynchronous Programming and Callbacks
+
+## Asynchronicity in Programming Languages
+
+Computers are asynchronous by design.
+
+Asynchronous means that things can happen independently of the main program flow.
+
+In the current consumer computers, every program runs for a specific time slot and then it stops its execution to let another program continue their execution. This thing runs in a cycle so fast that it's impossible to notice. We think our computers run many programs simultaneously, but this is an illusion (except on multiprocessor machines).
+
+Programs internally use _interrupts_, a signal that's emitted to the processor to gain the attention of the system.
+
+Let's not go into the internals of this now, but just keep in mind that it's normal for programs to be asynchronous and halt their execution until they need attention, allowing the computer to execute other things in the meantime. When a program is waiting for a response from the network, it cannot halt the processor until the request finishes.
+
+Normally, programming languages are synchronous and some provide a way to manage asynchronicity in the language or through libraries. C, Java, C#, PHP, Go, Ruby, Swift, and Python are all synchronous by default. Some of them handle async operations by using threads, spawning a new process.
+
+## JavaScript
+
+JavaScript is **synchronous** by default and is single threaded. This means that code cannot create new threads and run in parallel.
+
+Lines of code are executed in series, one after another, for example:
+
+```js
+const a = 1;
+const b = 2;
+const c = a * b;
+console.log(c);
+doSomething();
+```
+
+But JavaScript was born inside the browser, its main job, in the beginning, was to respond to user actions, like `onClick`, `onMouseOver`, `onChange`, `onSubmit` and so on. How could it do this with a synchronous programming model?
+
+The answer was in its environment. The **browser** provides a way to do it by providing a set of APIs that can handle this kind of functionality.
+
+More recently, Node.js introduced a non-blocking I/O environment to extend this concept to file access, network calls and so on.
+
+## Callbacks
+
+You can't know when a user is going to click a button. So, you **define an event handler for the click event**. This event handler accepts a function, which will be called when the event is triggered:
+
+```js
+document.getElementById('button').addEventListener('click', () => {
+  // item clicked
+});
+```
+
+This is the so-called **callback**.
+
+A callback is a simple function that's passed as a value to another function, and will only be executed when the event happens. We can do this because JavaScript has first-class functions, which can be assigned to variables and passed around to other functions (called **higher-order functions**)
+
+It's common to wrap all your client code in a `load` event listener on the `window` object, which runs the callback function only when the page is ready:
+
+```js
+window.addEventListener('load', () => {
+  // window loaded
+  // do what you want
+});
+```
+
+Callbacks are used everywhere, not just in DOM events.
+
+One common example is by using timers:
+
+```js
+setTimeout(() => {
+  // runs after 2 seconds
+}, 2000);
+```
+
+XHR requests also accept a callback, in this example by assigning a function to a property that will be called when a particular event occurs (in this case, the state of the request changes):
+
+```js
+const xhr = new XMLHttpRequest();
+xhr.onreadystatechange = () => {
+  if (xhr.readyState === 4) {
+    xhr.status === 200 ? console.log(xhr.responseText) : console.error('error');
+  }
+};
+xhr.open('GET', 'https://yoursite.com');
+xhr.send();
+```
+
+### Handling errors in callbacks
+
+How do you handle errors with callbacks? One very common strategy is to use what Node.js adopted: the first parameter in any callback function is the error object: **error-first callbacks**
+
+If there is no error, the object is `null`. If there is an error, it contains some description of the error and other information.
+
+```js
+const fs = require('fs');
+
+fs.readFile('/file.json', (err, data) => {
+  if (err) {
+    // handle error
+    console.log(err);
+    return;
+  }
+
+  // no errors, process data
+  console.log(data);
+});
+```
+
+### The problem with callbacks
+
+Callbacks are great for simple cases!
+
+However every callback adds a level of nesting, and when you have lots of callbacks, the code starts to be complicated very quickly:
+
+```js
+window.addEventListener('load', () => {
+  document.getElementById('button').addEventListener('click', () => {
+    setTimeout(() => {
+      items.forEach(item => {
+        // your code here
+      });
+    }, 2000);
+  });
+});
+```
+
+This is just a simple 4-levels code, but I've seen much more levels of nesting and it's not fun.
+
+How do we solve this?
+
+### Alternatives to callbacks
+
+Starting with ES6, JavaScript introduced several features that help us with asynchronous code that do not involve using callbacks: Promises (ES6) and Async/Await (ES2017).
diff --git a/pages/en/docs/guides/blocking-vs-non-blocking.md b/pages/en/learn/asynchronous-work/overview-of-blocking-vs-non-blocking.md
similarity index 96%
rename from pages/en/docs/guides/blocking-vs-non-blocking.md
rename to pages/en/learn/asynchronous-work/overview-of-blocking-vs-non-blocking.md
index 9fd8f2520d1b5..d4974c6e286a6 100644
--- a/pages/en/docs/guides/blocking-vs-non-blocking.md
+++ b/pages/en/learn/asynchronous-work/overview-of-blocking-vs-non-blocking.md
@@ -1,6 +1,7 @@
 ---
 title: Overview of Blocking vs Non-Blocking
-layout: docs.hbs
+layout: learn.hbs
+authors: ovflowd, HassanBahati
 ---
 
 # Overview of Blocking vs Non-Blocking
@@ -8,7 +9,7 @@ layout: docs.hbs
 This overview covers the difference between **blocking** and **non-blocking**
 calls in Node.js. This overview will refer to the event loop and libuv but no
 prior knowledge of those topics is required. Readers are assumed to have a
-basic understanding of the JavaScript language and Node.js callback pattern.
+basic understanding of the JavaScript language and Node.js [callback pattern](/learn/javascript-asynchronous-programming-and-callbacks/).
 
 > "I/O" refers primarily to interaction with the system's disk and
 > network supported by [libuv](https://libuv.org/).
@@ -40,6 +41,7 @@ Using the File System module as an example, this is a **synchronous** file read:
 
 ```js
 const fs = require('fs');
+
 const data = fs.readFileSync('/file.md'); // blocks here until file is read
 ```
 
@@ -47,6 +49,7 @@ And here is an equivalent **asynchronous** example:
 
 ```js
 const fs = require('fs');
+
 fs.readFile('/file.md', (err, data) => {
   if (err) throw err;
 });
@@ -63,6 +66,7 @@ Let's expand our example a little bit:
 
 ```js
 const fs = require('fs');
+
 const data = fs.readFileSync('/file.md'); // blocks here until file is read
 console.log(data);
 moreWork(); // will run after console.log
@@ -72,6 +76,7 @@ And here is a similar, but not equivalent asynchronous example:
 
 ```js
 const fs = require('fs');
+
 fs.readFile('/file.md', (err, data) => {
   if (err) throw err;
   console.log(data);
@@ -110,6 +115,7 @@ at an example:
 
 ```js
 const fs = require('fs');
+
 fs.readFile('/file.md', (err, data) => {
   if (err) throw err;
   console.log(data);
@@ -124,6 +130,7 @@ execute in the correct order is:
 
 ```js
 const fs = require('fs');
+
 fs.readFile('/file.md', (readFileErr, data) => {
   if (readFileErr) throw readFileErr;
   console.log(data);
diff --git a/pages/en/learn/asynchronous-work/the-nodejs-event-emitter.md b/pages/en/learn/asynchronous-work/the-nodejs-event-emitter.md
new file mode 100644
index 0000000000000..b0cbcfc6f278d
--- /dev/null
+++ b/pages/en/learn/asynchronous-work/the-nodejs-event-emitter.md
@@ -0,0 +1,70 @@
+---
+title: The Node.js Event emitter
+layout: learn.hbs
+authors: flaviocopes, MylesBorins, fhemberger, LaRuaNa, ahmadawais, ovflowd
+---
+
+# The Node.js Event emitter
+
+If you worked with JavaScript in the browser, you know how much of the interaction of the user is handled through events: mouse clicks, keyboard button presses, reacting to mouse movements, and so on.
+
+On the backend side, Node.js offers us the option to build a similar system using the [`events` module](/api/events/).
+
+This module, in particular, offers the `EventEmitter` class, which we'll use to handle our events.
+
+You initialize that using
+
+```js
+const EventEmitter = require('events');
+
+const eventEmitter = new EventEmitter();
+```
+
+This object exposes, among many others, the `on` and `emit` methods.
+
+- `emit` is used to trigger an event
+- `on` is used to add a callback function that's going to be executed when the event is triggered
+
+For example, let's create a `start` event, and as a matter of providing a sample, we react to that by just logging to the console:
+
+```js
+eventEmitter.on('start', () => {
+  console.log('started');
+});
+```
+
+When we run
+
+```js
+eventEmitter.emit('start');
+```
+
+the event handler function is triggered, and we get the console log.
+
+You can pass arguments to the event handler by passing them as additional arguments to `emit()`:
+
+```js
+eventEmitter.on('start', number => {
+  console.log(`started ${number}`);
+});
+
+eventEmitter.emit('start', 23);
+```
+
+Multiple arguments:
+
+```js
+eventEmitter.on('start', (start, end) => {
+  console.log(`started from ${start} to ${end}`);
+});
+
+eventEmitter.emit('start', 1, 100);
+```
+
+The EventEmitter object also exposes several other methods to interact with events, like
+
+- `once()`: add a one-time listener
+- `removeListener()` / `off()`: remove an event listener from an event
+- `removeAllListeners()`: remove all listeners for an event
+
+You can read more about these methods in the [official documentation](/api/events/).
diff --git a/pages/en/learn/asynchronous-work/understanding-processnexttick.md b/pages/en/learn/asynchronous-work/understanding-processnexttick.md
new file mode 100644
index 0000000000000..3424bd6ca5ca1
--- /dev/null
+++ b/pages/en/learn/asynchronous-work/understanding-processnexttick.md
@@ -0,0 +1,52 @@
+---
+title: Understanding process.nextTick()
+layout: learn.hbs
+authors: flaviocopes, MylesBorins, LaRuaNa, ahmadawais, ovflowd, marksist300
+---
+
+# Understanding process.nextTick()
+
+As you try to understand the Node.js event loop, one important part of it is `process.nextTick()`. Every time the event loop takes a full trip, we call it a tick.
+
+When we pass a function to `process.nextTick()`, we instruct the engine to invoke this function at the end of the current operation, before the next event loop tick starts:
+
+```js
+process.nextTick(() => {
+  // do something
+});
+```
+
+The event loop is busy processing the current function code. When this operation ends, the JS engine runs all the functions passed to `nextTick` calls during that operation.
+
+It's the way we can tell the JS engine to process a function asynchronously (after the current function), but as soon as possible, not queue it.
+
+Calling `setTimeout(() => {}, 0)` will execute the function at the end of next tick, much later than when using `nextTick()` which prioritizes the call and executes it just before the beginning of the next tick.
+
+Use `nextTick()` when you want to make sure that in the next event loop iteration that code is already executed.
+
+#### An Example of the order of events:
+
+```js
+console.log('Hello => number 1');
+
+setImmediate(() => {
+  console.log('Running before the timeout => number 3');
+});
+
+setTimeout(() => {
+  console.log('The timeout running last => number 4');
+}, 0);
+
+process.nextTick(() => {
+  console.log('Running at next tick => number 2');
+});
+```
+
+#### Output:
+
+```bash
+Hello => number 1
+Running at next tick => number 2
+Running before the timeout => number 3
+The timeout running last => number 4
+```
diff --git a/pages/en/learn/asynchronous-work/understanding-setimmediate.md b/pages/en/learn/asynchronous-work/understanding-setimmediate.md
new file mode 100644
index 0000000000000..3127ef6b82090
--- /dev/null
+++ b/pages/en/learn/asynchronous-work/understanding-setimmediate.md
@@ -0,0 +1,53 @@
+---
+title: Understanding setImmediate()
+layout: learn.hbs
+authors: flaviocopes, MylesBorins, LaRuaNa, ahmadawais, clean99, ovflowd
+---
+
+# Understanding setImmediate()
+
+When you want to execute some piece of code asynchronously, but as soon as possible, one option is to use the `setImmediate()` function provided by Node.js:
+
+```js
+setImmediate(() => {
+  // run something
+});
+```
+
+Any function passed as the setImmediate() argument is a callback that's executed in the next iteration of the event loop.
+
+How is `setImmediate()` different from `setTimeout(() => {}, 0)` (passing a 0ms timeout), and from `process.nextTick()` and `Promise.then()`?
+
+A function passed to `process.nextTick()` is going to be executed on the current iteration of the event loop, after the current operation ends. This means it will always execute before `setTimeout` and `setImmediate`.
+
+A `setTimeout()` callback with a 0ms delay is very similar to `setImmediate()`. The execution order will depend on various factors, but they will be both run in the next iteration of the event loop.
+
+A `process.nextTick` callback is added to `process.nextTick queue`. A `Promise.then()` callback is added to `promises microtask queue`. A `setTimeout`, `setImmediate` callback is added to `macrotask queue`.
+
+Event loop executes tasks in `process.nextTick queue` first, and then executes `promises microtask queue`, and then executes `macrotask queue`.
+
+Here is an example to show the order between `setImmediate()`, `process.nextTick()` and `Promise.then()`:
+
+```js
+const baz = () => console.log('baz');
+const foo = () => console.log('foo');
+const zoo = () => console.log('zoo');
+
+const start = () => {
+  console.log('start');
+  setImmediate(baz);
+  new Promise((resolve, reject) => {
+    resolve('bar');
+  }).then(resolve => {
+    console.log(resolve);
+    process.nextTick(zoo);
+  });
+  process.nextTick(foo);
+};
+
+start();
+
+// start foo bar zoo baz
+```
+
+This code will first call `start()`, then call `foo()` in `process.nextTick queue`. After that, it will handle `promises microtask queue`, which prints `bar` and adds `zoo()` in `process.nextTick queue` at the same time. Then it will call `zoo()` which has just been added. In the end, the `baz()` in `macrotask queue` is called.
diff --git a/pages/en/learn/command-line/accept-input-from-the-command-line-in-nodejs.md b/pages/en/learn/command-line/accept-input-from-the-command-line-in-nodejs.md
new file mode 100644
index 0000000000000..69dd019f90cc6
--- /dev/null
+++ b/pages/en/learn/command-line/accept-input-from-the-command-line-in-nodejs.md
@@ -0,0 +1,59 @@
+---
+title: Accept input from the command line in Node.js
+layout: learn.hbs
+authors: flaviocopes, MylesBorins, fhemberger, LaRuaNa, ahmadawais
+---
+
+# Accept input from the command line in Node.js
+
+How to make a Node.js CLI program interactive?
+
+Node.js since version 7 provides the [`readline` module](https://nodejs.org/api/readline.html) to perform exactly this: get input from a readable stream such as the `process.stdin` stream, which during the execution of a Node.js program is the terminal input, one line at a time.
+
+```js
+const readline = require('readline').createInterface({
+  input: process.stdin,
+  output: process.stdout,
+});
+
+readline.question(`What's your name?`, name => {
+  console.log(`Hi ${name}!`);
+  readline.close();
+});
+```
+
+This piece of code asks the user's _name_, and once the text is entered and the user presses enter, we send a greeting.
+
+The `question()` method shows the first parameter (a question) and waits for the user input. It calls the callback function once enter is pressed.
+
+In this callback function, we close the readline interface.
+
+`readline` offers several other methods, please check them out on the package documentation linked above.
+
+If you need to require a password, it's best not to echo it back, but instead show a `*` symbol.
+
+The simplest way is to use the [`readline-sync` package](https://www.npmjs.com/package/readline-sync) which is very similar in terms of the API and handles this out of the box.
+
+A more complete and abstract solution is provided by the [Inquirer.js package](https://github.com/SBoudrias/Inquirer.js).
+
+You can install it using `npm install inquirer`, and then you can replicate the above code like this:
+
+```js
+const inquirer = require('inquirer');
+
+const questions = [
+  {
+    type: 'input',
+    name: 'name',
+    message: "What's your name?",
+  },
+];
+
+inquirer.prompt(questions).then(answers => {
+  console.log(`Hi ${answers.name}!`);
+});
+```
+
+Inquirer.js lets you do many things like asking multiple choices, having radio buttons, confirmations, and more.
+
+It's worth knowing all the alternatives, especially the built-in ones provided by Node.js, but if you plan to take CLI input to the next level, Inquirer.js is an optimal choice.
diff --git a/pages/en/learn/command-line/how-to-read-environment-variables-from-nodejs.md b/pages/en/learn/command-line/how-to-read-environment-variables-from-nodejs.md
new file mode 100644
index 0000000000000..3033029c9d769
--- /dev/null
+++ b/pages/en/learn/command-line/how-to-read-environment-variables-from-nodejs.md
@@ -0,0 +1,49 @@
+---
+title: How to read environment variables from Node.js
+layout: learn.hbs
+authors: flaviocopes, MylesBorins, fhemberger, LaRuaNa, ahmadawais, manishprivet
+---
+
+# How to read environment variables from Node.js
+
+The `process` core module of Node.js provides the `env` property which hosts all the environment variables that were set at the moment the process was started.
+
+The below code runs `app.js` and set `USER_ID` and `USER_KEY`.
+
+```bash
+USER_ID=239482 USER_KEY=foobar node app.js
+```
+
+That will pass the user `USER_ID` as **239482** and the `USER_KEY` as **foobar**. This is suitable for testing, however for production, you will probably be configuring some bash scripts to export variables.
+
+> Note: `process` does not require a "require", it's automatically available.
+
+Here is an example that accesses the `USER_ID` and `USER_KEY` environment variables, which we set in above code.
+
+```js
+process.env.USER_ID; // "239482"
+process.env.USER_KEY; // "foobar"
+```
+
+In the same way you can access any custom environment variable you set.
+
+If you have multiple environment variables in your node project, you can also create an `.env` file in the root directory of your project, and then use the [dotenv](https://www.npmjs.com/package/dotenv) package to load them during runtime.
+
+```bash
+# .env file
+USER_ID="239482"
+USER_KEY="foobar"
+NODE_ENV="development"
+```
+
+In your js file
+
+```js
+require('dotenv').config();
+
+process.env.USER_ID; // "239482"
+process.env.USER_KEY; // "foobar"
+process.env.NODE_ENV; // "development"
+```
+
+> You can also run your js file with `node -r dotenv/config index.js` command if you don't want to import the package in your code.
diff --git a/pages/en/learn/command-line/how-to-use-the-nodejs-repl.md b/pages/en/learn/command-line/how-to-use-the-nodejs-repl.md
new file mode 100644
index 0000000000000..a8ac217d8b7bb
--- /dev/null
+++ b/pages/en/learn/command-line/how-to-use-the-nodejs-repl.md
@@ -0,0 +1,152 @@
+---
+title: How to use the Node.js REPL
+layout: learn.hbs
+authors: flaviocopes, MylesBorins, fhemberger, LaRuaNa, ahmadawais, vaishnav-mk
+---
+
+# How to use the Node.js REPL
+
+The `node` command is the one we use to run our Node.js scripts:
+
+```bash
+node script.js
+```
+
+If we run the `node` command without any script to execute or without any arguments, we start a REPL session:
+
+```bash
+node
+```
+
+> **Note:** `REPL` stands for Read Evaluate Print Loop, and it is a programming language environment (basically a console window) that takes single expression as user input and returns the result back to the console after execution. The REPL session provides a convenient way to quickly test simple JavaScript code.
+
+If you try it now in your terminal, this is what happens:
+
+```bash
+❯ node
+>
+```
+
+The command stays in idle mode and waits for us to enter something.
+
+> **Tip:** if you are unsure how to open your terminal, google "How to open terminal on your-operating-system".
+
+The REPL is waiting for us to enter some JavaScript code, to be more precise.
+
+Start simple and enter
+
+```console
+> console.log('test')
+test
+undefined
+>
+```
+
+The first value, `test`, is the output we told the console to print, then we get `undefined` which is the return value of running `console.log()`.
+Node read this line of code, evaluated it, printed the result, and then went back to waiting for more lines of code. Node will loop through these three steps for every piece of code we execute in the REPL until we exit the session. That is where the REPL got its name.
+
+Node automatically prints the result of any line of JavaScript code without the need to instruct it to do so. For example, type in the following line and press enter:
+
+```console
+> 5 === '5'
+false
+>
+```
+
+Note the difference in the outputs of the above two lines. The Node REPL printed `undefined` after executed `console.log()`, while on the other hand, it just printed the result of `5 === '5'`. You need to keep in mind that the former is just a statement in JavaScript, and the latter is an expression.
+
+In some cases, the code you want to test might need multiple lines. For example, say you want to define a function that generates a random number, in the REPL session type in the following line and press enter:
+
+```console
+function generateRandom() {
+...
+```
+
+The Node REPL is smart enough to determine that you are not done writing your code yet, and it will go into a multi-line mode for you to type in more code. Now finish your function definition and press enter:
+
+```console
+function generateRandom() {
+...return Math.random()
+}
+undefined
+```
+
+### The `_` special variable
+
+If after some code you type `_`, that is going to print the result of the last operation.
+
+### The Up arrow key
+
+If you press the `up` arrow key, you will get access to the history of the previous lines of code executed in the current, and even previous REPL sessions.
+
+### Dot commands
+
+The REPL has some special commands, all starting with a dot `.`. They are
+
+- `.help`: shows the dot commands help
+- `.editor`: enables editor mode, to write multiline JavaScript code with ease. Once you are in this mode, enter ctrl-D to run the code you wrote.
+- `.break`: when inputting a multi-line expression, entering the .break command will abort further input. Same as pressing ctrl-C.
+- `.clear`: resets the REPL context to an empty object and clears any multi-line expression currently being input.
+- `.load`: loads a JavaScript file, relative to the current working directory
+- `.save`: saves all you entered in the REPL session to a file (specify the filename)
+- `.exit`: exits the repl (same as pressing ctrl-C two times)
+
+The REPL knows when you are typing a multi-line statement without the need to invoke `.editor`.
+
+For example if you start typing an iteration like this:
+
+```console
+[1, 2, 3].forEach(num => {
+```
+
+and you press `enter`, the REPL will go to a new line that starts with 3 dots, indicating you can now continue to work on that block.
+
+```console
+... console.log(num)
+... })
+```
+
+If you type `.break` at the end of a line, the multiline mode will stop and the statement will not be executed.
+
+### Run REPL from JavaScript file
+
+We can import the REPL in a JavaScript file using `repl`.
+
+```js
+const repl = require('repl');
+```
+
+Using the repl variable we can perform various operations.
+To start the REPL command prompt, type in the following line
+
+```js
+repl.start();
+```
+
+Run the file in the command line.
+
+```bash
+node repl.js
+```
+
+```console
+> const n = 10
+```
+
+You can pass a string which shows when the REPL starts. The default is '> ' (with a trailing space), but we can define custom prompt.
+
+```js
+// a Unix style prompt
+const local = repl.start('$ ');
+```
+
+You can display a message while exiting the REPL
+
+```js
+local.on('exit', () => {
+  console.log('exiting repl');
+  process.exit();
+});
+```
+
+You can read more about the REPL module in the [repl documentation](/api/repl/).
diff --git a/pages/en/learn/command-line/output-to-the-command-line-using-nodejs.md b/pages/en/learn/command-line/output-to-the-command-line-using-nodejs.md
new file mode 100644
index 0000000000000..2cc6229d5c032
--- /dev/null
+++ b/pages/en/learn/command-line/output-to-the-command-line-using-nodejs.md
@@ -0,0 +1,209 @@
+---
+title: Output to the command line using Node.js
+layout: learn.hbs
+authors: flaviocopes, potch, MylesBorins, fhemberger, LaRuaNa, amiller-gh, ahmadawais
+---
+
+# Output to the command line using Node.js
+
+### Basic output using the console module
+
+Node.js provides a [`console` module](/api/console/) which provides tons of very useful ways to interact with the command line.
+
+It is basically the same as the `console` object you find in the browser.
+
+The most basic and most used method is `console.log()`, which prints the string you pass to it to the console.
+
+If you pass an object, it will render it as a string.
+
+You can pass multiple variables to `console.log`, for example:
+
+```js
+const x = 'x';
+const y = 'y';
+console.log(x, y);
+```
+
+and Node.js will print both.
+
+We can also format pretty phrases by passing variables and a format specifier.
+
+For example:
+
+```js
+console.log('My %s has %d ears', 'cat', 2);
+```
+
+- `%s` format a variable as a string
+- `%d` format a variable as a number
+- `%i` format a variable as its integer part only
+- `%o` format a variable as an object
+
+Example:
+
+```js
+console.log('%o', Number);
+```
+
+### Clear the console
+
+`console.clear()` clears the console (the behavior might depend on the console used)
+
+### Counting elements
+
+`console.count()` is a handy method.
+
+Take this code:
+
+```js
+const x = 1;
+const y = 2;
+const z = 3;
+
+console.count(
+  'The value of x is ' + x + ' and has been checked .. how many times?'
+);
+
+console.count(
+  'The value of x is ' + x + ' and has been checked .. how many times?'
+);
+
+console.count(
+  'The value of y is ' + y + ' and has been checked .. how many times?'
+);
+```
+
+What happens is that `console.count()` will count the number of times a string is printed, and print the count next to it:
+
+You can just count apples and oranges:
+
+```js
+const oranges = ['orange', 'orange'];
+const apples = ['just one apple'];
+oranges.forEach(fruit => {
+  console.count(fruit);
+});
+apples.forEach(fruit => {
+  console.count(fruit);
+});
+```
+
+### Reset counting
+
+The console.countReset() method resets counter used with console.count().
+
+We will use the apples and orange example to demonstrate this.
+
+```js
+const oranges = ['orange', 'orange'];
+const apples = ['just one apple'];
+oranges.forEach(fruit => {
+  console.count(fruit);
+});
+apples.forEach(fruit => {
+  console.count(fruit);
+});
+
+console.countReset('orange');
+
+oranges.forEach(fruit => {
+  console.count(fruit);
+});
+```
+
+Notice how the call to `console.countReset('orange')` resets the value counter to zero.
+
+### Print the stack trace
+
+There might be cases where it's useful to print the call stack trace of a function, maybe to answer the question _how did you reach that part of the code?_
+
+You can do so using `console.trace()`:
+
+```js
+const function2 = () => console.trace();
+const function1 = () => function2();
+function1();
+```
+
+This will print the stack trace. This is what's printed if we try this in the Node.js REPL:
+
+```bash
+Trace
+    at function2 (repl:1:33)
+    at function1 (repl:1:25)
+    at repl:1:1
+    at ContextifyScript.Script.runInThisContext (vm.js:44:33)
+    at REPLServer.defaultEval (repl.js:239:29)
+    at bound (domain.js:301:14)
+    at REPLServer.runBound [as eval] (domain.js:314:12)
+    at REPLServer.onLine (repl.js:440:10)
+    at emitOne (events.js:120:20)
+    at REPLServer.emit (events.js:210:7)
+```
+
+### Calculate the time spent
+
+You can easily calculate how much time a function takes to run, using `time()` and `timeEnd()`
+
+```js
+const doSomething = () => console.log('test');
+const measureDoingSomething = () => {
+  console.time('doSomething()');
+  // do something, and measure the time it takes
+  doSomething();
+  console.timeEnd('doSomething()');
+};
+measureDoingSomething();
+```
+
+### stdout and stderr
+
+As we saw console.log is great for printing messages in the Console. This is what's called the standard output, or `stdout`.
+
+`console.error` prints to the `stderr` stream.
+
+It will not appear in the console, but it will appear in the error log.
+
+### Color the output
+
+You can color the output of your text in the console by using [escape sequences](https://gist.github.com/iamnewton/8754917). An escape sequence is a set of characters that identifies a color.
+
+Example:
+
+```js
+console.log('\x1b[33m%s\x1b[0m', 'hi!');
+```
+
+You can try that in the Node.js REPL, and it will print `hi!` in yellow.
+
+However, this is the low-level way to do this. The simplest way to go about coloring the console output is by using a library. [Chalk](https://github.com/chalk/chalk) is such a library, and in addition to coloring it also helps with other styling facilities, like making text bold, italic or underlined.
+
+You install it with `npm install chalk@4`, then you can use it:
+
+```js
+const chalk = require('chalk');
+
+console.log(chalk.yellow('hi!'));
+```
+
+Using `chalk.yellow` is much more convenient than trying to remember the escape codes, and the code is much more readable.
+
+Check the project link posted above for more usage examples.
+
+### Create a progress bar
+
+[Progress](https://www.npmjs.com/package/progress) is an awesome package to create a progress bar in the console. Install it using `npm install progress`
+
+This snippet creates a 10-step progress bar, and every 100ms one step is completed. When the bar completes we clear the interval:
+
+```js
+const ProgressBar = require('progress');
+
+const bar = new ProgressBar(':bar', { total: 10 });
+const timer = setInterval(() => {
+  bar.tick();
+  if (bar.complete) {
+    clearInterval(timer);
+  }
+}, 100);
+```
diff --git a/pages/en/learn/command-line/run-nodejs-scripts-from-the-command-line.md b/pages/en/learn/command-line/run-nodejs-scripts-from-the-command-line.md
new file mode 100644
index 0000000000000..2785722c48ea5
--- /dev/null
+++ b/pages/en/learn/command-line/run-nodejs-scripts-from-the-command-line.md
@@ -0,0 +1,71 @@
+---
+title: Run Node.js scripts from the command line
+layout: learn.hbs
+authors: flaviocopes, MylesBorins, fhemberger, LaRuaNa, ahmadawais, akazyti
+---
+
+# Run Node.js scripts from the command line
+
+The usual way to run a Node.js program is to run the globally available `node` command (once you install Node.js) and pass the name of the file you want to execute.
+
+If your main Node.js application file is `app.js`, you can call it by typing:
+
+```bash
+node app.js
+```
+
+Above, you are explicitly telling the shell to run your script with `node`. You can also embed this information into your JavaScript file with a "shebang" line. The "shebang" is the first line in the file, and tells the OS which interpreter to use for running the script. Below is the first line of JavaScript:
+
+```js
+#!/usr/bin/node
+```
+
+Above, we are explicitly giving the absolute path of interpreter. Not all operating systems have `node` in the bin folder, but all should have `env`. You can tell the OS to run `env` with node as parameter:
+
+```js
+#!/usr/bin/env node
+
+// your code
+```
+
+To use a shebang, your file should have executable permission. You can give `app.js` the executable permission by running:
+
+```bash
+chmod u+x app.js
+```
+
+While running the command, make sure you are in the same directory which contains the `app.js` file.
+
+## Pass string as argument to `node` instead of file path
+
+To execute a string as argument you can use `-e`, `--eval "script"`. Evaluate the following argument as JavaScript. The modules which are predefined in the REPL can also be used in script.
+
+On Windows, using cmd.exe a single quote will not work correctly because it only recognizes double `"` for quoting. In Powershell or Git bash, both `'` and `"` are usable.
+
+```bash
+node -e "console.log(123)"
+```
+
+## Restart the application automatically
+
+The `node` command has to be re-executed in bash whenever there is a change in the application. To restart the application automatically, use the `nodemon` module.
+
+Install the nodemon module globally to system path:
+
+```bash
+npm i -g nodemon
+```
+
+You can also install nodemon as a development dependency:
+
+```bash
+npm i --save-dev nodemon
+```
+
+This local installation of nodemon can be run by calling it from within npm script such as npm start or using npx nodemon.
+
+Run the application using the `nodemon` command followed by the application's file name:
+
+```bash
+nodemon app.js
+```
diff --git a/pages/en/learn/getting-started/an-introduction-to-the-npm-package-manager.md b/pages/en/learn/getting-started/an-introduction-to-the-npm-package-manager.md
new file mode 100644
index 0000000000000..e1e840b715906
--- /dev/null
+++ b/pages/en/learn/getting-started/an-introduction-to-the-npm-package-manager.md
@@ -0,0 +1,131 @@
+---
+title: An introduction to the NPM package manager
+layout: learn.hbs
+authors: flaviocopes, MylesBorins, LaRuaNa, jgb-solutions, amiller-gh, ahmadawais
+---
+
+# An introduction to the NPM package manager
+
+## Introduction to npm
+
+`npm` is the standard package manager for Node.js.
+
+In September 2022 over 2.1 million packages were reported being listed in the npm registry, making it the biggest single language code repository on Earth, and you can be sure there is a package for (almost!) everything.
+
+It started as a way to download and manage dependencies of Node.js packages, but it has since become a tool used also in frontend JavaScript.
+
+> [**Yarn**](https://yarnpkg.com/en/) and [**pnpm**](https://pnpm.io) are alternatives to npm cli. You can check them out as well.
+
+## Packages
+
+`npm` manages downloads of dependencies of your project.
+
+### Installing all dependencies
+
+If a project has a `package.json` file, by running
+
+```bash
+npm install
+```
+
+it will install everything the project needs, in the `node_modules` folder, creating it if it's not existing already.
+
+### Installing a single package
+
+You can also install a specific package by running
+
+```bash
+npm install <package-name>
+```
+
+Furthermore, since npm 5, this command adds `<package-name>` to the `package.json` file _dependencies_. Before version 5, you needed to add the flag `--save`.
+
+Often you'll see more flags added to this command:
+
+- `--save-dev` installs and adds the entry to the `package.json` file _devDependencies_
+- `--no-save` installs but does not add the entry to the `package.json` file _dependencies_
+- `--save-optional` installs and adds the entry to the `package.json` file _optionalDependencies_
+- `--no-optional` will prevent optional dependencies from being installed
+
+Shorthands of the flags can also be used:
+
+- \-S: `--save`
+- \-D: `--save-dev`
+- \-O: `--save-optional`
+
+The difference between _devDependencies_ and _dependencies_ is that the former contains development tools, like a testing library, while the latter is bundled with the app in production.
+
+As for the _optionalDependencies_ the difference is that build failure of the dependency will not cause installation to fail. But it is your program's responsibility to handle the lack of the dependency. Read more about [optional dependencies](https://docs.npmjs.com/cli/v7/configuring-npm/package-json#optionaldependencies).
+
+### Updating packages
+
+Updating is also made easy, by running
+
+```bash
+npm update
+```
+
+`npm` will check all packages for a newer version that satisfies your versioning constraints.
+
+You can specify a single package to update as well:
+
+```bash
+npm update <package-name>
+```
+
+## Versioning
+
+In addition to plain downloads, `npm` also manages **versioning**, so you can specify any specific version of a package, or require a version higher or lower than what you need.
+
+Many times you'll find that a library is only compatible with a major release of another library.
+
+Or a bug in the latest release of a lib, still unfixed, is causing an issue.
+
+Specifying an explicit version of a library also helps to keep everyone on the same exact version of a package, so that the whole team runs the same version until the `package.json` file is updated.
+
+In all those cases, versioning helps a lot, and `npm` follows the semantic versioning (semver) standard.
+
+You can install a specific version of a package, by running
+
+```bash
+npm install <package-name>@<version>
+```
+
+## Running Tasks
+
+The package.json file supports a format for specifying command line tasks that can be run by using
+
+```bash
+npm run <task-name>
+```
+
+For example:
+
+```json
+{
+  "scripts": {
+    "start-dev": "node lib/server-development",
+    "start": "node lib/server-production"
+  }
+}
+```
+
+It's very common to use this feature to run Webpack:
+
+```json
+{
+  "scripts": {
+    "watch": "webpack --watch --progress --colors --config webpack.conf.js",
+    "dev": "webpack --progress --colors --config webpack.conf.js",
+    "prod": "NODE_ENV=production webpack -p --config webpack.conf.js"
+  }
+}
+```
+
+So instead of typing those long commands, which are easy to forget or mistype, you can run
+
+```console
+$ npm run watch
+$ npm run dev
+$ npm run prod
+```
diff --git a/pages/en/learn/getting-started/differences-between-nodejs-and-the-browser.md b/pages/en/learn/getting-started/differences-between-nodejs-and-the-browser.md
new file mode 100644
index 0000000000000..f841ee5647b7c
--- /dev/null
+++ b/pages/en/learn/getting-started/differences-between-nodejs-and-the-browser.md
@@ -0,0 +1,27 @@
+---
+title: Differences between Node.js and the Browser
+layout: learn.hbs
+authors: flaviocopes, ollelauribostrom, MylesBorins, fhemberger, LaRuaNa, ahmadawais, karlhorky
+---
+
+# Differences between Node.js and the Browser
+
+Both the browser and Node.js use JavaScript as their programming language. Building apps that run in the browser is a completely different thing than building a Node.js application. Despite the fact that it's always JavaScript, there are some key differences that make the experience radically different.
+
+From the perspective of a frontend developer who extensively uses JavaScript, Node.js apps bring with them a huge advantage: the comfort of programming everything - the frontend and the backend - in a single language.
+
+You have a huge opportunity because we know how hard it is to fully, deeply learn a programming language, and by using the same language to perform all your work on the web - both on the client and on the server, you're in a unique position of advantage.
+
+> **What changes is the ecosystem.**
+
+In the browser, most of the time what you are doing is interacting with the DOM, or other Web Platform APIs like Cookies. Those do not exist in Node.js, of course. You don't have the `document`, `window` and all the other objects that are provided by the browser.
+
+And in the browser, we don't have all the nice APIs that Node.js provides through its modules, like the filesystem access functionality.
+
+Another big difference is that in Node.js you control the environment. Unless you are building an open source application that anyone can deploy anywhere, you know which version of Node.js you will run the application on. Compared to the browser environment, where you don't get the luxury to choose what browser your visitors will use, this is very convenient.
+
+This means that you can write all the modern ES2015+ JavaScript that your Node.js version supports. Since JavaScript moves so fast, but browsers can be a bit slow to upgrade, sometimes on the web you are stuck with using older JavaScript / ECMAScript releases. You can use Babel to transform your code to be ES5-compatible before shipping it to the browser, but in Node.js, you won't need that.
+
+Another difference is that Node.js supports both the CommonJS and ES module systems (since Node.js v12), while in the browser we are starting to see the ES Modules standard being implemented.
+
+In practice, this means that you can use both `require()` and `import` in Node.js, while you are limited to `import` in the browser.
diff --git a/pages/en/learn/getting-started/ecmascript-2015-es6-and-beyond.md b/pages/en/learn/getting-started/ecmascript-2015-es6-and-beyond.md
new file mode 100644
index 0000000000000..73692db280510
--- /dev/null
+++ b/pages/en/learn/getting-started/ecmascript-2015-es6-and-beyond.md
@@ -0,0 +1,41 @@
+---
+title: ECMAScript 2015 (ES6) and beyond
+layout: learn.hbs
+authors: ovflowd
+---
+
+# ECMAScript 2015 (ES6) and beyond
+
+Node.js is built against modern versions of [V8](https://v8.dev/). By keeping up-to-date with the latest releases of this engine, we ensure new features from the [JavaScript ECMA-262 specification](http://www.ecma-international.org/publications/standards/Ecma-262.htm) are brought to Node.js developers in a timely manner, as well as continued performance and stability improvements.
+
+All ECMAScript 2015 (ES6) features are split into three groups for **shipping**, **staged**, and **in progress** features:
+
+- All **shipping** features, which V8 considers stable, are turned **on by default on Node.js** and do **NOT** require any kind of runtime flag.
+- **Staged** features, which are almost-completed features that are not considered stable by the V8 team, require a runtime flag: `--harmony`.
+- **In progress** features can be activated individually by their respective harmony flag, although this is highly discouraged unless for testing purposes. Note: these flags are exposed by V8 and will potentially change without any deprecation notice.
+
+### Which features ship with which Node.js version by default?
+
+The website [node.green](https://node.green/) provides an excellent overview over supported ECMAScript features in various versions of Node.js, based on kangax's compat-table.
+
+### Which features are in progress?
+
+New features are constantly being added to the V8 engine. Generally speaking, expect them to land on a future Node.js release, although timing is unknown.
+
+You may list all the _in progress_ features available on each Node.js release by grepping through the `--v8-options` argument. Please note that these are incomplete and possibly broken features of V8, so use them at your own risk:
+
+```bash
+node --v8-options | grep "in progress"
+```
+
+### I have my infrastructure set up to leverage the --harmony flag. Should I remove it?
+
+The current behavior of the `--harmony` flag on Node.js is to enable **staged** features only. After all, it is now a synonym of `--es_staging`. As mentioned above, these are completed features that have not been considered stable yet. If you want to play safe, especially on production environments, consider removing this runtime flag until it ships by default on V8 and, consequently, on Node.js. If you keep this enabled, you should be prepared for further Node.js upgrades to break your code if V8 changes their semantics to more closely follow the standard.
+
+### How do I find which version of V8 ships with a particular version of Node.js?
+
+Node.js provides a simple way to list all dependencies and respective versions that ship with a specific binary through the `process` global object. In case of the V8 engine, type the following in your terminal to retrieve its version:
+
+```bash
+node -p process.versions.v8
+```
diff --git a/pages/en/learn/getting-started/how-much-javascript-do-you-need-to-know-to-use-nodejs.md b/pages/en/learn/getting-started/how-much-javascript-do-you-need-to-know-to-use-nodejs.md
new file mode 100644
index 0000000000000..67b5dda382f64
--- /dev/null
+++ b/pages/en/learn/getting-started/how-much-javascript-do-you-need-to-know-to-use-nodejs.md
@@ -0,0 +1,39 @@
+---
+title: 'How much JavaScript do you need to know to use Node.js?'
+layout: learn.hbs
+authors: flaviocopes, ollelauribostrom, MylesBorins, fhemberger, LaRuaNa, ahmadawais, elanandkumar, ovflowd, vaishnav-mk
+---
+
+# How much JavaScript do you need to know to use Node.js?
+
+As a beginner, it's hard to get to a point where you are confident enough in your programming abilities. While learning to code, you might also be confused at where does JavaScript end, and where Node.js begins, and vice versa.
+
+### What is recommended to learn before diving deep with Node.js?
+
+- [Lexical Structure](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Lexical_grammar)
+- [Expressions](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators)
+- [Data Types](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Data_structures)
+- [Classes](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Classes)
+- [Variables](https://developer.mozilla.org/en-US/docs/Learn/JavaScript/First_steps/Variables#what_is_a_variable)
+- [Functions](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Guide/Functions)
+- [`this` operator](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/this)
+- [Arrow Functions](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Functions/Arrow_functions)
+- [Loops](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Guide/Loops_and_iteration)
+- [Scopes](https://developer.mozilla.org/en-US/docs/Glossary/Scope)
+- [Arrays](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array)
+- [Template Literals](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Template_literals)
+- [Strict Mode](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Strict_mode)
+- [ECMAScript 2015 (ES6) and beyond](/learn/ecmascript-2015-es6-and-beyond/)
+
+With those concepts in mind, you are well on your road to become a proficient JavaScript developer, in both the browser and in Node.js.
+
+#### Asynchronous Programming
+
+The following concepts are also key to understand asynchronous programming, which is one of the fundamental parts of Node.js:
+
+- [Asynchronous programming and callbacks](https://developer.mozilla.org/en-US/docs/Learn/JavaScript/Asynchronous/Introducing)
+- [Timers](https://developer.mozilla.org/en-US/docs/Web/API/setTimeout)
+- [Promises](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Guide/Using_promises)
+- [Async and Await](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/async_function)
+- [Closures](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Closures)
+- [The Event Loop](https://developer.mozilla.org/en-US/docs/Web/JavaScript/EventLoop)
diff --git a/pages/en/learn/getting-started/how-to-install-nodejs.md b/pages/en/learn/getting-started/how-to-install-nodejs.md
new file mode 100644
index 0000000000000..40f72f70043e5
--- /dev/null
+++ b/pages/en/learn/getting-started/how-to-install-nodejs.md
@@ -0,0 +1,17 @@
+---
+title: How to install Node.js
+layout: learn.hbs
+authors: flaviocopes, ZYSzys, ollelauribostrom, MylesBorins, fhemberger, LaRuaNa, ahmadawais, benhalverson, ovflowd
+---
+
+# How to install Node.js
+
+Node.js can be installed in different ways. This post highlights the most common and convenient ones. Official packages for all the major platforms are available at [https://nodejs.dev/download/](/download/).
+
+One very convenient way to install Node.js is through a package manager. In this case, every operating system has its own. Other package managers for MacOS, Linux, and Windows are listed in [https://nodejs.dev/download/package-manager/](/download/package-manager/)
+
+`nvm` is a popular way to run Node.js. It allows you to easily switch the Node.js version, and install new versions to try and easily rollback if something breaks. It is also very useful to test your code with old Node.js versions.
+
+> See [https://github.com/nvm-sh/nvm](https://github.com/nvm-sh/nvm) for more information about this option.
+
+In any case, when Node.js is installed you'll have access to the `node` executable program in the command line.
diff --git a/pages/en/learn/getting-started/introduction-to-nodejs.md b/pages/en/learn/getting-started/introduction-to-nodejs.md
new file mode 100644
index 0000000000000..0042aa4c346f4
--- /dev/null
+++ b/pages/en/learn/getting-started/introduction-to-nodejs.md
@@ -0,0 +1,84 @@
+---
+title: Introduction to Node.js
+layout: learn.hbs
+authors: flaviocopes, potch, MylesBorins, RomainLanz, virkt25, Trott, onel0p3z, ollelauribostrom, MarkPieszak, fhemberger, LaRuaNa, FrozenPandaz, mcollina, amiller-gh, ahmadawais, saqibameen, dangen-effy, aymen94, benhalverson
+---
+
+# Introduction to Node.js
+
+Node.js is an open-source and cross-platform JavaScript runtime environment. It is a popular tool for almost any kind of project!
+
+Node.js runs the V8 JavaScript engine, the core of Google Chrome, outside of the browser. This allows Node.js to be very performant.
+
+A Node.js app runs in a single process, without creating a new thread for every request. Node.js provides a set of asynchronous I/O primitives in its standard library that prevent JavaScript code from blocking and generally, libraries in Node.js are written using non-blocking paradigms, making blocking behavior the exception rather than the norm.
+
+When Node.js performs an I/O operation, like reading from the network, accessing a database or the filesystem, instead of blocking the thread and wasting CPU cycles waiting, Node.js will resume the operations when the response comes back.
+
+This allows Node.js to handle thousands of concurrent connections with a single server without introducing the burden of managing thread concurrency, which could be a significant source of bugs.
+
+Node.js has a unique advantage because millions of frontend developers that write JavaScript for the browser are now able to write the server-side code in addition to the client-side code without the need to learn a completely different language.
+
+In Node.js the new ECMAScript standards can be used without problems, as you don't have to wait for all your users to update their browsers - you are in charge of deciding which ECMAScript version to use by changing the Node.js version, and you can also enable specific experimental features by running Node.js with flags.
+
+## An Example Node.js Application
+
+The most common example Hello World of Node.js is a web server:
+
+```js
+const http = require('http');
+
+const hostname = '127.0.0.1';
+const port = 3000;
+
+const server = http.createServer((req, res) => {
+  res.statusCode = 200;
+  res.setHeader('Content-Type', 'text/plain');
+  res.end('Hello World\n');
+});
+
+server.listen(port, hostname, () => {
+  console.log(`Server running at http://${hostname}:${port}/`);
+});
+```
+
+To run this snippet, save it as a `server.js` file and run `node server.js` in your terminal.
+
+This code first includes the Node.js [`http` module](https://nodejs.org/api/http.html).
+
+Node.js has a fantastic [standard library](https://nodejs.org/api/), including first-class support for networking.
+
+The `createServer()` method of `http` creates a new HTTP server and returns it.
+
+The server is set to listen on the specified port and host name. When the server is ready, the callback function is called, in this case informing us that the server is running.
+
+Whenever a new request is received, the [`request` event](https://nodejs.org/api/http.html#http_event_request) is called, providing two objects: a request (an [`http.IncomingMessage`](https://nodejs.org/api/http.html#http_class_http_incomingmessage) object) and a response (an [`http.ServerResponse`](https://nodejs.org/api/http.html#http_class_http_serverresponse) object).
+
+Those 2 objects are essential to handle the HTTP call.
+
+The first provides the request details. In this simple example, this is not used, but you could access the request headers and request data.
+
+The second is used to return data to the caller.
+
+In this case with:
+
+```js
+res.statusCode = 200;
+```
+
+we set the statusCode property to 200, to indicate a successful response.
+
+We set the Content-Type header:
+
+```js
+res.setHeader('Content-Type', 'text/plain');
+```
+
+and we close the response, adding the content as an argument to `end()`:
+
+```js
+res.end('Hello World\n');
+```
+
+### More Examples
+
+See https://github.com/nodejs/examples for a list of Node.js examples that go beyond hello world.
diff --git a/pages/en/learn/getting-started/nodejs-the-difference-between-development-and-production.md b/pages/en/learn/getting-started/nodejs-the-difference-between-development-and-production.md
new file mode 100644
index 0000000000000..d9f097df63328
--- /dev/null
+++ b/pages/en/learn/getting-started/nodejs-the-difference-between-development-and-production.md
@@ -0,0 +1,63 @@
+---
+title: Node.js, the difference between development and production
+layout: learn.hbs
+authors: flaviocopes, MylesBorins, fhemberger, LaRuaNa, ahmadawais, RenanTKN
+---
+
+# Node.js, the difference between development and production
+
+You can have different configurations for production and development environments.
+
+Node.js assumes it's always running in a development environment.
+You can signal Node.js that you are running in production by setting the `NODE_ENV=production` environment variable.
+
+This is usually done by executing the command
+
+```bash
+export NODE_ENV=production
+```
+
+in the shell, but it's better to put it in your shell configuration file (e.g. `.bash_profile` with the Bash shell) because otherwise the setting does not persist in case of a system restart.
+
+You can also apply the environment variable by prepending it to your application initialization command:
+
+```bash
+NODE_ENV=production node app.js
+```
+
+This environment variable is a convention that is widely used in external libraries as well.
+
+Setting the environment to `production` generally ensures that
+
+- logging is kept to a minimum, essential level
+- more caching levels take place to optimize performance
+
+For example [Pug](https://pugjs.org), the templating library used by [Express](https://expressjs.com), compiles in debug mode if `NODE_ENV` is not set to `production`. Express views are compiled in every request in development mode, while in production they are cached. There are many more examples.
+
+You can use conditional statements to execute code in different environments:
+
+```js
+if (process.env.NODE_ENV === 'development') {
+  // ...
+}
+
+if (process.env.NODE_ENV === 'production') {
+  // ...
+}
+
+if (['production', 'staging'].includes(process.env.NODE_ENV)) {
+  // ...
+}
+```
+
+For example, in an Express app, you can use this to set different error handlers per environment:
+
+```js
+if (process.env.NODE_ENV === 'development') {
+  app.use(express.errorHandler({ dumpExceptions: true, showStack: true }));
+}
+
+if (process.env.NODE_ENV === 'production') {
+  app.use(express.errorHandler());
+}
+```
diff --git a/pages/en/learn/getting-started/nodejs-with-typescript.md b/pages/en/learn/getting-started/nodejs-with-typescript.md
new file mode 100644
index 0000000000000..c26534ee24dd4
--- /dev/null
+++ b/pages/en/learn/getting-started/nodejs-with-typescript.md
@@ -0,0 +1,132 @@
+---
+title: Node.js with TypeScript
+layout: learn.hbs
+authors: sbielenica, ovflowd, vaishnav-mk
+---
+
+# Node.js with TypeScript
+
+## What is TypeScript
+
+**[TypeScript](https://www.typescriptlang.org)** is a trendy open-source language maintained and developed by Microsoft. It's loved and used by a lot of software developers around the world.
+
+Basically, it's a superset of JavaScript that adds new capabilities to the language. The most notable addition is static type definitions, something that is not present in plain JavaScript. Thanks to types, it's possible, for example, to declare what kind of arguments we are expecting and what is returned exactly in our functions or what's the exact shape of the object that we are creating. TypeScript is a really powerful tool and opens a new world of possibilities in JavaScript projects. It makes our code more secure and robust by preventing many bugs before the code is even shipped - it catches problems during code development and integrates wonderfully with code editors like Visual Studio Code.
+
+We can talk about other TypeScript benefits later, let's see some examples now!
+
+### Examples
+
+Take a look at this code snippet and then we can unpack it together:
+
+```ts
+type User = {
+  name: string;
+  age: number;
+};
+
+function isAdult(user: User): boolean {
+  return user.age >= 18;
+}
+
+const justine: User = {
+  name: 'Justine',
+  age: 23,
+};
+
+const isJustineAnAdult: boolean = isAdult(justine);
+```
+
+The first part (with the `type` keyword) is responsible for declaring our custom object type representing users. Later we utilize this newly created type to create function `isAdult` that accepts one argument of type `User` and returns `boolean`. After this, we create `justine`, our example data that can be used for calling the previously defined function. Finally, we create a new variable with information on whether `justine` is an adult.
+
+There are additional things about this example that you should know. Firstly, if we would not comply with declared types, TypeScript would alarm us that something is wrong and prevent misuse. Secondly, not everything must be typed explicitly - TypeScript is very smart and can deduce types for us. For example, variable `isJustineAnAdult` would be of type `boolean` even if we didn't type it explicitly or `justine` would be valid argument for our function even if we didn't declare this variable as of `User` type.
+
+Okay, so we have some TypeScript code. Now how do we run it?
+
+**First thing to do is to install TypeScript in our project:**
+
+```bash
+npm i -D typescript
+```
+
+Now we can compile it to JavaScript using `tsc` command in the terminal. Let's do it!
+
+**Assuming that our file is named `example.ts`, the command would look like:**
+
+```bash
+npx tsc example.ts
+```
+
+> [npx](https://www.npmjs.com/package/npx) here stands for Node Package Execute. This tool allows us to run TypeScript's compiler without installing it globally.
+
+`tsc` is the TypeScript compiler which will take our TypeScript code and compile it to JavaScript.
+This command will result in a new file named `example.js` that we can run using Node.js.
+Now when we know how to compile and run TypeScript code let's see TypeScript bug-preventing capabilities in action!
+
+**This is how we will modify our code:**
+
+```ts
+type User = {
+  name: string;
+  age: number;
+};
+
+function isAdult(user: User): boolean {
+  return user.age >= 18;
+}
+
+const justine: User = {
+  name: 'Justine',
+  age: 'Secret!',
+};
+
+const isJustineAnAdult: string = isAdult(justine, "I shouldn't be here!");
+```
+
+**And this is what TypeScript has to say about this:**
+
+```console
+example.ts:12:3 - error TS2322: Type 'string' is not assignable to type 'number'.
+
+12   age: "Secret!",
+     ~~~
+
+  example.ts:3:3
+    3   age: number;
+        ~~~
+    The expected type comes from property 'age' which is declared here on type 'User'
+
+example.ts:15:7 - error TS2322: Type 'boolean' is not assignable to type 'string'.
+
+15 const isJustineAnAdult: string = isAdult(justine, "I shouldn't be here!");
+         ~~~~~~~~~~~~~~~~
+
+example.ts:15:51 - error TS2554: Expected 1 arguments, but got 2.
+
+15 const isJustineAnAdult: string = isAdult(justine, "I shouldn't be here!");
+                                                     ~~~~~~~~~~~~~~~~~~~~~~
+
+
+Found 3 errors.
+```
+
+As you can see TypeScript successfully prevents us from shipping code that could work unexpectedly. That's wonderful!
+
+## More about TypeScript
+
+TypeScript offers a whole lot of other great mechanisms like interfaces, classes, utility types and so on. Also, on bigger projects you can declare your TypeScript compiler configuration in a separate file and granularly adjust how it works, how strict it is and where it stores compiled files for example. You can read more about all this awesome stuff in [the official TypeScript docs](https://www.typescriptlang.org/docs).
+
+Some of the other benefits of TypeScript that are worth mentioning are that it can be adopted progressively, it helps making code more readable and understandable and it allows developers to use modern language features while shipping code for older Node.js versions.
+
+## TypeScript in the Node.js world
+
+TypeScript is well-established in the Node.js world and used by many companies, open-source projects, tools and frameworks.
+Some of the notable examples of open-source projects using TypeScript are:
+
+- [NestJS](https://nestjs.com/) - robust and fully-featured framework that makes creating scalable and well-architected systems easy and pleasant
+- [TypeORM](https://typeorm.io/#/) - great ORM influenced by other well-known tools from other languages like Hibernate, Doctrine or Entity Framework
+- [Prisma](https://prisma.io/) - next-generation ORM featuring a declarative data model, generated migrations and fully type-safe database queries
+- [RxJS](https://rxjs.dev/) - widely used library for reactive programming
+- [AdonisJS](https://adonisjs.com) - A fully featured web framework with Node.js
+- [FoalTs](https://foalts.org/) - The Elegant Nodejs Framework
+
+And many, many more great projects... Maybe even your next one!
diff --git a/pages/en/learn/getting-started/nodejs-with-webassembly.md b/pages/en/learn/getting-started/nodejs-with-webassembly.md
new file mode 100644
index 0000000000000..a18683a4c9a69
--- /dev/null
+++ b/pages/en/learn/getting-started/nodejs-with-webassembly.md
@@ -0,0 +1,69 @@
+---
+title: Node.js with WebAssembly
+layout: learn.hbs
+authors: lancemccluskey, ovflowd
+---
+
+# Node.js with WebAssembly
+
+**[WebAssembly](https://webassembly.org)** is a high-performance assembly-like language that can be compiled from various languages, including C/C++, Rust, and AssemblyScript. Currently, it is supported by Chrome, Firefox, Safari, Edge, and Node.js!
+
+The WebAssembly specification details two file formats, a binary format called a WebAssembly Module with a `.wasm` extension and corresponding text representation called WebAssembly Text format with a `.wat` extension.
+
+## Key Concepts
+
+- Module - A compiled WebAssembly binary, ie a `.wasm` file.
+- Memory - A resizable ArrayBuffer.
+- Table - A resizable typed array of references not stored in Memory.
+- Instance - An instantiation of a Module with its Memory, Table, and variables.
+
+In order to use WebAssembly, you need a `.wasm` binary file and a set of APIs to communicate with WebAssembly. Node.js provides the necessary APIs via the global `WebAssembly` object.
+
+```js
+console.log(WebAssembly);
+/*
+Object [WebAssembly] {
+  compile: [Function: compile],
+  validate: [Function: validate],
+  instantiate: [Function: instantiate]
+}
+*/
+```
+
+## Generating WebAssembly Modules
+
+There are multiple methods available to generate WebAssembly binary files including:
+
+- Writing WebAssembly (`.wat`) by hand and converting to binary format using tools such as [wabt](https://github.com/webassembly/wabt)
+- Using [emscripten](https://emscripten.org/) with a C/C++ application
+- Using [wasm-pack](https://rustwasm.github.io/wasm-pack/book/) with a Rust application
+- Using [AssemblyScript](https://www.assemblyscript.org/) if you prefer a TypeScript-like experience
+
+> Some of these tools generate not only the binary file, but the JavaScript "glue" code and corresponding HTML files to run in the browser.
+
+## How to use it
+
+Once you have a WebAssembly module, you can use the Node.js `WebAssembly` object to instantiate it.
+
+```js
+// Assume add.wasm file exists that contains a single function adding 2 provided arguments
+const fs = require('fs');
+
+const wasmBuffer = fs.readFileSync('/path/to/add.wasm');
+WebAssembly.instantiate(wasmBuffer).then(wasmModule => {
+  // Exported function live under instance.exports
+  const { add } = wasmModule.instance.exports;
+  const sum = add(5, 6);
+  console.log(sum); // Outputs: 11
+});
+```
+
+## Interacting with the OS
+
+WebAssembly modules cannot directly access OS functionality on its own. A third-party tool [Wasmtime](https://docs.wasmtime.dev/) can be used to access this functionality. `Wasmtime` utilizes the [WASI](https://wasi.dev/) API to access the OS functionality.
+
+## Resources
+
+- [General WebAssembly Information](https://webassembly.org/)
+- [MDN Docs](https://developer.mozilla.org/en-US/docs/WebAssembly)
+- [Write WebAssembly by hand](https://webassembly.github.io/spec/core/text/index.html)
diff --git a/pages/en/learn/getting-started/the-v8-javascript-engine.md b/pages/en/learn/getting-started/the-v8-javascript-engine.md
new file mode 100644
index 0000000000000..821df8d93a314
--- /dev/null
+++ b/pages/en/learn/getting-started/the-v8-javascript-engine.md
@@ -0,0 +1,51 @@
+---
+title: The V8 JavaScript Engine
+layout: learn.hbs
+authors: flaviocopes, smfoote, co16353sidak, MylesBorins, LaRuaNa, andys8, ahmadawais, karlhorky, aymen94
+---
+
+# The V8 JavaScript Engine
+
+V8 is the name of the JavaScript engine that powers Google Chrome. It's the thing that takes our JavaScript and executes it while browsing with Chrome.
+
+V8 is the JavaScript engine i.e. it parses and executes JavaScript code. The DOM, and the other Web Platform APIs (they all makeup runtime environment) are provided by the browser.
+
+The cool thing is that the JavaScript engine is independent of the browser in which it's hosted. This key feature enabled the rise of Node.js. V8 was chosen to be the engine that powered Node.js back in 2009, and as the popularity of Node.js exploded, V8 became the engine that now powers an incredible amount of server-side code written in JavaScript.
+
+The Node.js ecosystem is huge and thanks to V8 which also powers desktop apps, with projects like Electron.
+
+## Other JS engines
+
+Other browsers have their own JavaScript engine:
+
+- Firefox has [**SpiderMonkey**](https://spidermonkey.dev)
+- Safari has [**JavaScriptCore**](https://developer.apple.com/documentation/javascriptcore) (also called Nitro)
+- Edge was originally based on [**Chakra**](https://github.com/Microsoft/ChakraCore) but has more recently been [rebuilt using Chromium](https://support.microsoft.com/en-us/help/4501095/download-the-new-microsoft-edge-based-on-chromium) and the V8 engine.
+
+and many others exist as well.
+
+All those engines implement the [ECMA ES-262 standard](https://www.ecma-international.org/publications/standards/Ecma-262.htm), also called ECMAScript, the standard used by JavaScript.
+
+## The quest for performance
+
+V8 is written in C++, and it's continuously improved. It is portable and runs on Mac, Windows, Linux and several other systems.
+
+In this V8 introduction, we will ignore the implementation details of V8: they can be found on more authoritative sites (e.g. the [V8 official site](https://v8.dev/)), and they change over time, often radically.
+
+V8 is always evolving, just like the other JavaScript engines around, to speed up the Web and the Node.js ecosystem.
+
+On the web, there is a race for performance that's been going on for years, and we (as users and developers) benefit a lot from this competition because we get faster and more optimized machines year after year.
+
+## Compilation
+
+JavaScript is generally considered an interpreted language, but modern JavaScript engines no longer just interpret JavaScript, they compile it.
+
+This has been happening since 2009, when the SpiderMonkey JavaScript compiler was added to Firefox 3.5, and everyone followed this idea.
+
+JavaScript is internally compiled by V8 with **just-in-time** (JIT) **compilation** to speed up the execution.
+
+This might seem counter-intuitive, but since the introduction of Google Maps in 2004, JavaScript has evolved from a language that was generally executing a few dozens of lines of code to complete applications with thousands to hundreds of thousands of lines running in the browser.
+
+Our applications can now run for hours inside a browser, rather than being just a few form validation rules or simple scripts.
+
+In this _new world_, compiling JavaScript makes perfect sense because while it might take a little bit more to have the JavaScript _ready_, once done it's going to be much more performant than purely interpreted code.
diff --git a/pages/en/learn/index.md b/pages/en/learn/index.md
new file mode 100644
index 0000000000000..be9f17eb1ae51
--- /dev/null
+++ b/pages/en/learn/index.md
@@ -0,0 +1,46 @@
+---
+title: Learn Node.js
+layout: learn.hbs
+---
+
+# Learn Node.js®
+
+## Getting Started
+
+- [Introduction to Node.js](/learn/getting-started/introduction-to-nodejs)
+- [How to install Node.js](/learn/getting-started/how-to-install-nodejs)
+- [How much JavaScript do you need to know to use Node.js?](/learn/getting-started/how-much-javascript-do-you-need-to-know-to-use-nodejs)
+- [Differences between Node.js and the Browser](/learn/getting-started/differences-between-nodejs-and-the-browser)
+- [The V8 JavaScript Engine](/learn/getting-started/the-v8-javascript-engine)
+- [An introduction to the NPM package manager](/learn/getting-started/an-introduction-to-the-npm-package-manager)
+- [ECMAScript 2015 (ES6) and beyond](/learn/getting-started/ecmascript-2015-es6-and-beyond)
+- [Node.js, the difference between development and production](/learn/getting-started/nodejs-the-difference-between-development-and-production)
+- [Node.js with TypeScript](/learn/getting-started/nodejs-with-typescript)
+- [Node.js with WebAssembly](/learn/getting-started/nodejs-with-webassembly)
+
+## Asynchronous Work
+
+- [Asynchronous flow control](/learn/asynchronous-work/asynchronous-flow-control)
+- [Overview of Blocking vs Non-Blocking](/learn/asynchronous-work/overview-of-blocking-vs-non-blocking)
+- [JavaScript Asynchronous Programming and Callbacks](/learn/asynchronous-work/javascript-asynchronous-programming-and-callbacks)
+- [Discover JavaScript Timers](/learn/asynchronous-work/discover-javascript-timers)
+- [Understanding process.nextTick()](/learn/asynchronous-work/understanding-processnexttick)
+- [Understanding setImmediate()](/learn/asynchronous-work/understanding-setimmediate)
+- [The Node.js Event emitter](/learn/asynchronous-work/the-nodejs-event-emitter)
+
+## Manipulating Files
+
+- [Node.js file stats](/learn/manipulating-files/nodejs-file-stats)
+- [Node.js File Paths](/learn/manipulating-files/nodejs-file-paths)
+- [Working with file descriptors in Node.js](/learn/manipulating-files/working-with-file-descriptors-in-nodejs)
+- [Reading files with Node.js](/learn/manipulating-files/reading-files-with-nodejs)
+- [Writing files with Node.js](/learn/manipulating-files/writing-files-with-nodejs)
+- [Working with folders in Node.js](/learn/manipulating-files/working-with-folders-in-nodejs)
+
+## Command Line
+
+- [Run Node.js scripts from the command line](/learn/command-line/run-nodejs-scripts-from-the-command-line)
+- [How to read environment variables from Node.js](/learn/command-line/how-to-read-environment-variables-from-nodejs)
+- [How to use the Node.js REPL](/learn/command-line/how-to-use-the-nodejs-repl)
+- [Output to the command line using Node.js](/learn/command-line/output-to-the-command-line-using-nodejs)
+- [Accept input from the command line in Node.js](/learn/command-line/accept-input-from-the-command-line-in-nodejs)
diff --git a/pages/en/learn/manipulating-files/nodejs-file-paths.md b/pages/en/learn/manipulating-files/nodejs-file-paths.md
new file mode 100644
index 0000000000000..06d521f1c298c
--- /dev/null
+++ b/pages/en/learn/manipulating-files/nodejs-file-paths.md
@@ -0,0 +1,72 @@
+---
+title: Node.js File Paths
+layout: learn.hbs
+authors: flaviocopes, MylesBorins, fhemberger, LaRuaNa, amiller-gh, ahmadawais
+---
+
+# Node.js File Paths
+
+Every file in the system has a path. On Linux and macOS, a path might look like: `/users/joe/file.txt` while Windows computers are different, and have a structure such as: `C:\users\joe\file.txt`
+
+You need to pay attention when using paths in your applications, as this difference must be taken into account.
+
+You include this module in your files using `const path = require('path');` and you can start using its methods.
+
+## Getting information out of a path
+
+Given a path, you can extract information out of it using those methods:
+
+- `dirname`: gets the parent folder of a file
+- `basename`: gets the filename part
+- `extname`: gets the file extension
+
+### Example
+
+```js
+const notes = '/users/joe/notes.txt';
+
+path.dirname(notes); // /users/joe
+path.basename(notes); // notes.txt
+path.extname(notes); // .txt
+```
+
+You can get the file name without the extension by specifying a second argument to `basename`:
+
+```js
+path.basename(notes, path.extname(notes)); // notes
+```
+
+## Working with paths
+
+You can join two or more parts of a path by using `path.join()`:
+
+```js
+const name = 'joe';
+path.join('/', 'users', name, 'notes.txt'); // '/users/joe/notes.txt'
+```
+
+You can get the absolute path calculation of a relative path using `path.resolve()`:
+
+```js
+path.resolve('joe.txt'); // '/Users/joe/joe.txt' if run from my home folder
+```
+
+In this case Node.js will simply append `/joe.txt` to the current working directory. If you specify a second parameter folder, `resolve` will use the first as a base for the second:
+
+```js
+path.resolve('tmp', 'joe.txt'); // '/Users/joe/tmp/joe.txt' if run from my home folder
+```
+
+If the first parameter starts with a slash, that means it's an absolute path:
+
+```js
+path.resolve('/etc', 'joe.txt'); // '/etc/joe.txt'
+```
+
+`path.normalize()` is another useful function, that will try and calculate the actual path, when it contains relative specifiers like `.` or `..`, or double slashes:
+
+```js
+path.normalize('/users/joe/..//test.txt'); // '/users/test.txt'
+```
+
+**Neither resolve nor normalize will check if the path exists**. They just calculate a path based on the information they got.
diff --git a/pages/en/learn/manipulating-files/nodejs-file-stats.md b/pages/en/learn/manipulating-files/nodejs-file-stats.md
new file mode 100644
index 0000000000000..36c1247cec29c
--- /dev/null
+++ b/pages/en/learn/manipulating-files/nodejs-file-stats.md
@@ -0,0 +1,81 @@
+---
+title: Node.js file stats
+layout: learn.hbs
+authors: flaviocopes, ZYSzys, MylesBorins, fhemberger, LaRuaNa, ahmadawais, clean99, ovflowd, vaishnav-mk
+---
+
+# Node.js file stats
+
+Every file comes with a set of details that we can inspect using Node.js. In particular, using the `stat()` method provided by the [`fs` module](/api/fs/).
+
+You call it passing a file path, and once Node.js gets the file details it will call the callback function you pass, with 2 parameters: an error message, and the file stats:
+
+```js
+const fs = require('fs');
+
+fs.stat('/Users/joe/test.txt', (err, stats) => {
+  if (err) {
+    console.error(err);
+  }
+  // we have access to the file stats in `stats`
+});
+```
+
+Node.js also provides a sync method, which blocks the thread until the file stats are ready:
+
+```js
+const fs = require('fs');
+
+try {
+  const stats = fs.statSync('/Users/joe/test.txt');
+} catch (err) {
+  console.error(err);
+}
+```
+
+The file information is included in the stats variable. What kind of information can we extract using the stats?
+
+**A lot, including:**
+
+- if the file is a directory or a file, using `stats.isFile()` and `stats.isDirectory()`
+- if the file is a symbolic link using `stats.isSymbolicLink()`
+- the file size in bytes using `stats.size`.
+
+There are other advanced methods, but the bulk of what you'll use in your day-to-day programming is this.
+
+```js
+const fs = require('fs');
+
+fs.stat('/Users/joe/test.txt', (err, stats) => {
+  if (err) {
+    console.error(err);
+    return;
+  }
+
+  stats.isFile(); // true
+  stats.isDirectory(); // false
+  stats.isSymbolicLink(); // false
+  stats.size; // 1024000 //= 1MB
+});
+```
+
+You can also use promise-based `fsPromises.stat()` method offered by the `fs/promises` module if you like:
+
+```js
+const fs = require('fs/promises');
+
+async function example() {
+  try {
+    const stats = await fs.stat('/Users/joe/test.txt');
+    stats.isFile(); // true
+    stats.isDirectory(); // false
+    stats.isSymbolicLink(); // false
+    stats.size; // 1024000 //= 1MB
+  } catch (err) {
+    console.log(err);
+  }
+}
+example();
+```
+
+You can read more about the `fs` module in the [official documentation](/api/fs/).
diff --git a/pages/en/learn/manipulating-files/reading-files-with-nodejs.md b/pages/en/learn/manipulating-files/reading-files-with-nodejs.md
new file mode 100644
index 0000000000000..e087302d87e73
--- /dev/null
+++ b/pages/en/learn/manipulating-files/reading-files-with-nodejs.md
@@ -0,0 +1,56 @@
+---
+title: Reading files with Node.js
+layout: learn.hbs
+authors: flaviocopes, MylesBorins, fhemberger, LaRuaNa, ahmadawais, clean99
+---
+
+# Reading files with Node.js
+
+The simplest way to read a file in Node.js is to use the `fs.readFile()` method, passing it the file path, encoding and a callback function that will be called with the file data (and the error):
+
+```js
+const fs = require('fs');
+
+fs.readFile('/Users/joe/test.txt', 'utf8', (err, data) => {
+  if (err) {
+    console.error(err);
+    return;
+  }
+  console.log(data);
+});
+```
+
+Alternatively, you can use the synchronous version `fs.readFileSync()`:
+
+```js
+const fs = require('fs');
+
+try {
+  const data = fs.readFileSync('/Users/joe/test.txt', 'utf8');
+  console.log(data);
+} catch (err) {
+  console.error(err);
+}
+```
+
+You can also use the promise-based `fsPromises.readFile()` method offered by the `fs/promises` module:
+
+```js
+const fs = require('fs/promises');
+
+async function example() {
+  try {
+    const data = await fs.readFile('/Users/joe/test.txt', { encoding: 'utf8' });
+    console.log(data);
+  } catch (err) {
+    console.log(err);
+  }
+}
+example();
+```
+
+All three of `fs.readFile()`, `fs.readFileSync()` and `fsPromises.readFile()` read the full content of the file in memory before returning the data.
+
+This means that big files are going to have a major impact on your memory consumption and speed of execution of the program.
+
+In this case, a better option is to read the file content using streams.
diff --git a/pages/en/learn/manipulating-files/working-with-file-descriptors-in-nodejs.md b/pages/en/learn/manipulating-files/working-with-file-descriptors-in-nodejs.md
new file mode 100644
index 0000000000000..b7b9c3723a8dd
--- /dev/null
+++ b/pages/en/learn/manipulating-files/working-with-file-descriptors-in-nodejs.md
@@ -0,0 +1,102 @@
+---
+title: Working with file descriptors in Node.js
+layout: learn.hbs
+authors: flaviocopes, MylesBorins, fhemberger, LaRuaNa, ahmadawais, clean99, vaishnav-mk
+---
+
+# Working with file descriptors in Node.js
+
+Before you're able to interact with a file that sits in your filesystem, you must get a file descriptor.
+
+A file descriptor is a reference to an open file, a number (fd) returned by opening the file using the `open()` method offered by the `fs` module. This number (`fd`) uniquely identifies an open file in operating system:
+
+```js
+const fs = require('fs');
+
+fs.open('/Users/joe/test.txt', 'r', (err, fd) => {
+  // fd is our file descriptor
+});
+```
+
+Notice the `r` we used as the second parameter to the `fs.open()` call.
+
+That flag means we open the file for reading.
+
+**Other flags you'll commonly use are:**
+
+<table>
+  <tr>
+    <th>Flag</th>
+    <th>Description</th>
+    <th>File gets created if it doesn't exist</th>
+  </tr>
+  <tr>
+    <td><code>r+</code></td>
+    <td>This flag opens the file for <b>reading</b> and <b>writing</b></td>
+    <td style="text-align: center;">❌</td>
+  </tr>
+  <tr>
+    <td><code>w+</code></td>
+    <td>This flag opens the file for <b>reading</b> and <b>writing</b> and it also positions the stream at the <b>beginning</b> of the file</td>
+    <td style="text-align: center;">✅</td>
+  </tr>
+  <tr>
+    <td><code>a</code></td>
+    <td>This flag opens the file for <b>writing</b> and it also positions the stream at the <b>end</b> of the file</td>
+    <td style="text-align: center;">✅</td>
+  </tr>
+  <tr>
+    <td><code>a+</code></td>
+    <td>This flag opens the file for <b>reading</b> and <b>writing</b> and it also positions the stream at the <b>end</b> of the file</td>
+    <td style="text-align: center;">✅</td>
+  </tr>
+</table>
+
+You can also open the file by using the `fs.openSync` method, which returns the file descriptor, instead of providing it in a callback:
+
+```js
+const fs = require('fs');
+
+try {
+  const fd = fs.openSync('/Users/joe/test.txt', 'r');
+} catch (err) {
+  console.error(err);
+}
+```
+
+Once you get the file descriptor, in whatever way you choose, you can perform all the operations that require it, like calling `fs.close()` and many other operations that interact with the filesystem.
+
+You can also open the file by using the promise-based `fsPromises.open` method offered by the `fs/promises` module.
+
+The `fs/promises` module is available starting only from Node.js v14. Before v14, after v10, you can use `require('fs').promises` instead. Before v10, after v8, you can use `util.promisify` to convert `fs` methods into promise-based methods.
+
+```js
+const fs = require('fs/promises');
+// Or const fs = require('fs').promises before v14.
+async function example() {
+  let filehandle;
+  try {
+    filehandle = await fs.open('/Users/joe/test.txt', 'r');
+    console.log(filehandle.fd);
+    console.log(await filehandle.readFile({ encoding: 'utf8' }));
+  } finally {
+    if (filehandle) await filehandle.close();
+  }
+}
+example();
+```
+
+Here is an example of `util.promisify`:
+
+```js
+const fs = require('fs');
+const util = require('util');
+
+async function example() {
+  const open = util.promisify(fs.open);
+  const fd = await open('/Users/joe/test.txt', 'r');
+}
+example();
+```
+
+To see more details about the `fs/promises` module, please check [fs/promises API](/api/fs/#promise-example).
diff --git a/pages/en/learn/manipulating-files/working-with-folders-in-nodejs.md b/pages/en/learn/manipulating-files/working-with-folders-in-nodejs.md
new file mode 100644
index 0000000000000..c35dabf701e31
--- /dev/null
+++ b/pages/en/learn/manipulating-files/working-with-folders-in-nodejs.md
@@ -0,0 +1,141 @@
+---
+title: Working with folders in Node.js
+layout: learn.hbs
+authors: flaviocopes, MylesBorins, fhemberger, liangpeili, LaRuaNa, ahmadawais, clean99
+---
+
+# Working with folders in Node.js
+
+The Node.js `fs` core module provides many handy methods you can use to work with folders.
+
+## Check if a folder exists
+
+Use `fs.access()` (and its promise-based `fsPromises.access()` counterpart) to check if the folder exists and Node.js can access it with its permissions.
+
+## Create a new folder
+
+Use `fs.mkdir()` or `fs.mkdirSync()` or `fsPromises.mkdir()` to create a new folder.
+
+```js
+const fs = require('fs');
+
+const folderName = '/Users/joe/test';
+
+try {
+  if (!fs.existsSync(folderName)) {
+    fs.mkdirSync(folderName);
+  }
+} catch (err) {
+  console.error(err);
+}
+```
+
+## Read the content of a directory
+
+Use `fs.readdir()` or `fs.readdirSync()` or `fsPromises.readdir()` to read the contents of a directory.
+
+This piece of code reads the content of a folder, both files and subfolders, and returns their relative path:
+
+```js
+const fs = require('fs');
+
+const folderPath = '/Users/joe';
+
+fs.readdirSync(folderPath);
+```
+
+You can get the full path:
+
+```js
+fs.readdirSync(folderPath).map(fileName => {
+  return path.join(folderPath, fileName);
+});
+```
+
+You can also filter the results to only return the files, and exclude the folders:
+
+```js
+const isFile = fileName => {
+  return fs.lstatSync(fileName).isFile();
+};
+
+fs.readdirSync(folderPath)
+  .map(fileName => {
+    return path.join(folderPath, fileName);
+  })
+  .filter(isFile);
+```
+
+## Rename a folder
+
+Use `fs.rename()` or `fs.renameSync()` or `fsPromises.rename()` to rename folder. The first parameter is the current path, the second the new path:
+
+```js
+const fs = require('fs');
+
+fs.rename('/Users/joe', '/Users/roger', err => {
+  if (err) {
+    console.error(err);
+  }
+  // done
+});
+```
+
+`fs.renameSync()` is the synchronous version:
+
+```js
+const fs = require('fs');
+
+try {
+  fs.renameSync('/Users/joe', '/Users/roger');
+} catch (err) {
+  console.error(err);
+}
+```
+
+`fsPromises.rename()` is the promise-based version:
+
+```js
+const fs = require('fs/promises');
+
+async function example() {
+  try {
+    await fs.rename('/Users/joe', '/Users/roger');
+  } catch (err) {
+    console.log(err);
+  }
+}
+example();
+```
+
+## Remove a folder
+
+Use `fs.rmdir()` or `fs.rmdirSync()` or `fsPromises.rmdir()` to remove a folder.
+
+```js
+const fs = require('fs');
+
+fs.rmdir(dir, err => {
+  if (err) {
+    throw err;
+  }
+
+  console.log(`${dir} is deleted!`);
+});
+```
+
+To remove a folder that has contents use `fs.rm()` with the option `{ recursive: true }` to recursively remove the contents.
+
+`{ recursive: true, force: true }` makes it so that exceptions will be ignored if the folder does not exist.
+
+```js
+const fs = require('fs');
+
+fs.rm(dir, { recursive: true, force: true }, err => {
+  if (err) {
+    throw err;
+  }
+
+  console.log(`${dir} is deleted!`);
+});
+```
diff --git a/pages/en/learn/manipulating-files/writing-files-with-nodejs.md b/pages/en/learn/manipulating-files/writing-files-with-nodejs.md
new file mode 100644
index 0000000000000..4ea4f3d430749
--- /dev/null
+++ b/pages/en/learn/manipulating-files/writing-files-with-nodejs.md
@@ -0,0 +1,115 @@
+---
+title: Writing files with Node.js
+layout: learn.hbs
+authors: flaviocopes, MylesBorins, fhemberger, LaRuaNa, ahmadawais, clean99, ovflowd, vaishnav-mk
+---
+
+# Writing files with Node.js
+
+## Writing a file
+
+The easiest way to write to files in Node.js is to use the `fs.writeFile()` API.
+
+```js
+const fs = require('fs');
+
+const content = 'Some content!';
+
+fs.writeFile('/Users/joe/test.txt', content, err => {
+  if (err) {
+    console.error(err);
+  }
+  // file written successfully
+});
+```
+
+### Writing a file synchronously
+
+Alternatively, you can use the synchronous version `fs.writeFileSync()`:
+
+```js
+const fs = require('fs');
+
+const content = 'Some content!';
+
+try {
+  fs.writeFileSync('/Users/joe/test.txt', content);
+  // file written successfully
+} catch (err) {
+  console.error(err);
+}
+```
+
+You can also use the promise-based `fsPromises.writeFile()` method offered by the `fs/promises` module:
+
+```js
+const fs = require('fs/promises');
+
+async function example() {
+  try {
+    const content = 'Some content!';
+    await fs.writeFile('/Users/joe/test.txt', content);
+  } catch (err) {
+    console.log(err);
+  }
+}
+example();
+```
+
+By default, this API will **replace the contents of the file** if it does already exist.
+
+**You can modify the default by specifying a flag:**
+
+```js
+fs.writeFile('/Users/joe/test.txt', content, { flag: 'a+' }, err => {});
+```
+
+#### The flags you'll likely use are
+
+| Flag | Description                                                                                                                | File gets created if it doesn't exist |
+| ---- | -------------------------------------------------------------------------------------------------------------------------- | :-----------------------------------: |
+| `r+` | This flag opens the file for **reading** and **writing**                                                                   |                  ❌                   |
+| `w+` | This flag opens the file for **reading** and **writing** and it also positions the stream at the **beginning** of the file |                  ✅                   |
+| `a`  | This flag opens the file for **writing** and it also positions the stream at the **end** of the file                       |                  ✅                   |
+| `a+` | This flag opens the file for **reading** and **writing** and it also positions the stream at the **end** of the file       |                  ✅                   |
+
+- You can find more information about the flags in the [fs documentation](/api/fs/#file-system-flags).
+
+## Appending content to a file
+
+Appending to files is handy when you don't want to overwrite a file with new content, but rather add to it.
+
+### Examples
+
+A handy method to append content to the end of a file is `fs.appendFile()` (and its `fs.appendFileSync()` counterpart):
+
+```js
+const fs = require('fs');
+
+const content = 'Some content!';
+
+fs.appendFile('file.log', content, err => {
+  if (err) {
+    console.error(err);
+  }
+  // done!
+});
+```
+
+#### Example with Promises
+
+Here is a `fsPromises.appendFile()` example:
+
+```js
+const fs = require('fs/promises');
+
+async function example() {
+  try {
+    const content = 'Some content!';
+    await fs.appendFile('/Users/joe/test.txt', content);
+  } catch (err) {
+    console.log(err);
+  }
+}
+example();
+```
diff --git a/providers/layoutProvider.tsx b/providers/layoutProvider.tsx
index 3e2f71e11368f..f89e68f23a98f 100644
--- a/providers/layoutProvider.tsx
+++ b/providers/layoutProvider.tsx
@@ -11,6 +11,7 @@ import DocsLayout from '@/layouts/DocsLayout';
 import DownloadCurrentLayout from '@/layouts/DownloadCurrentLayout';
 import DownloadLayout from '@/layouts/DownloadLayout';
 import IndexLayout from '@/layouts/IndexLayout';
+import LearnLayout from '@/layouts/LearnLayout';
 import type { LegacyFrontMatter, LegacyLayouts } from '@/types';
 
 type LayoutContextProps = {
@@ -25,6 +26,8 @@ const getLegacyLayout = (layout: LegacyLayouts) => {
   switch (layout) {
     case 'about.hbs':
       return AboutLayout;
+    case 'learn.hbs':
+      return LearnLayout;
     case 'blog-index.hbs':
       return BlogIndexLayout;
     case 'blog-post.hbs':
diff --git a/public/static/images/learn/javascript-timers/recursive-settimeout.png b/public/static/images/learn/javascript-timers/recursive-settimeout.png
new file mode 100644
index 0000000000000..fd9fd5dfd6e03
Binary files /dev/null and b/public/static/images/learn/javascript-timers/recursive-settimeout.png differ
diff --git a/public/static/images/learn/javascript-timers/setinterval-ok.png b/public/static/images/learn/javascript-timers/setinterval-ok.png
new file mode 100644
index 0000000000000..8d45f06ee2160
Binary files /dev/null and b/public/static/images/learn/javascript-timers/setinterval-ok.png differ
diff --git a/public/static/images/learn/javascript-timers/setinterval-overlapping.png b/public/static/images/learn/javascript-timers/setinterval-overlapping.png
new file mode 100644
index 0000000000000..155cc0b0a2995
Binary files /dev/null and b/public/static/images/learn/javascript-timers/setinterval-overlapping.png differ
diff --git a/public/static/images/learn/javascript-timers/setinterval-varying-duration.png b/public/static/images/learn/javascript-timers/setinterval-varying-duration.png
new file mode 100644
index 0000000000000..d4b4e05b62b65
Binary files /dev/null and b/public/static/images/learn/javascript-timers/setinterval-varying-duration.png differ
diff --git a/redirects.json b/redirects.json
index 83c5cadcf710b..bc96f6fd995a4 100644
--- a/redirects.json
+++ b/redirects.json
@@ -161,6 +161,18 @@
     {
       "source": "/:locale/about/security",
       "destination": "/:locale/about/security-reporting"
+    },
+    {
+      "source": "/:locale/docs/guides/getting-started-guide",
+      "destination": "/:locale/learn/getting-started/introduction-to-nodejs"
+    },
+    {
+      "source": "/:locale/docs/guides/blocking-vs-non-blocking",
+      "destination": "/:locale/learn/asynchronous-work/overview-of-blocking-vs-non-blocking"
+    },
+    {
+      "source": "/:locale/docs/guides/timers-in-node/",
+      "destination": "/:locale/learn/asynchronous-work/discover-javascript-timers"
     }
   ]
 }
diff --git a/styles/old/index.css b/styles/old/index.css
index 033c3766c6953..2d04d9d2bf1b1 100644
--- a/styles/old/index.css
+++ b/styles/old/index.css
@@ -47,41 +47,46 @@ article a {
   }
 }
 
-.has-side-nav {
-  nav {
-    float: left;
-    margin-top: 1.5em;
-    width: 200px;
-
-    ul {
-      list-style-type: none;
-      margin: 0;
-      padding: 0;
-    }
+#main {
+  .has-side-nav {
+    nav {
+      margin-top: 1.5em;
+      min-width: 200px;
+      max-width: 250px;
+      flex: 1 0;
+
+      ul {
+        list-style-type: none;
+        margin: 0;
+        padding: 0;
+      }
 
-    li {
-      padding: 0.1em 0.5em;
-    }
+      li {
+        padding: 0.1em 0.5em;
+      }
 
-    a {
-      display: block;
-      line-height: 1;
-      margin-left: -10px;
-      margin-right: -10px;
-      padding: 5px 10px;
-    }
+      a {
+        display: block;
+        line-height: 1;
+        margin-left: -10px;
+        margin-right: -10px;
+        padding: 5px 10px;
+      }
 
-    .active {
-      > a,
-      > a:hover {
-        background-color: $active-green;
-        color: $white;
+      .active {
+        > a,
+        > a:hover {
+          background-color: $active-green;
+          color: $white;
+        }
       }
     }
-  }
 
-  article {
-    margin-left: 220px;
+    article {
+      margin: 0 20px;
+      overflow: hidden;
+      flex: 1 1;
+    }
   }
 }
 
@@ -91,19 +96,6 @@ article a {
   margin: 0.5em 0;
 }
 
-@media screen and (max-width: 480px) {
-  .has-side-nav {
-    nav {
-      float: none;
-      width: 100%;
-    }
-
-    article {
-      margin-left: 0;
-    }
-  }
-}
-
 .color-lightgray {
   color: $light-gray;
 }
@@ -135,18 +127,26 @@ a:hover .color-lightgray {
   }
 }
 
-html[dir='rtl'] {
-  .has-side-nav {
-    nav {
-      float: right;
+@media screen and (max-width: 1002px) {
+  #main {
+    article {
+      ul:not(.no-padding) {
+        margin: 0 20px;
+      }
     }
+  }
+}
 
-    article {
-      margin-left: 0;
-      margin-right: 220px;
+@media screen and (max-width: 480px) {
+  #main {
+    .has-side-nav {
+      nav {
+        max-width: 100%;
+      }
 
-      @media screen and (max-width: 480px) {
-        margin-right: 0;
+      article {
+        margin: 0;
+        width: 100%;
       }
     }
   }
diff --git a/styles/old/layout/grid.css b/styles/old/layout/grid.css
index e64c603d59972..b2ab83ba857ce 100644
--- a/styles/old/layout/grid.css
+++ b/styles/old/layout/grid.css
@@ -1,7 +1,6 @@
 .container {
   margin: 0 auto;
   max-width: $body-max-width;
-  overflow: hidden;
   width: 100%;
 }
 
diff --git a/styles/old/layout/main.css b/styles/old/layout/main.css
index caa5945a70ebd..e028d6b5b6ced 100644
--- a/styles/old/layout/main.css
+++ b/styles/old/layout/main.css
@@ -1,19 +1,26 @@
 #main {
   .container {
-    padding: 0 20px;
+    display: flex;
+  }
+
+  .has-side-nav.container {
+    flex-direction: row;
   }
 }
 
-@media screen and (max-width: 768px) {
+@media screen and (max-width: 1002px) {
   #main {
     .container {
-      padding: 1em 20px;
+      margin: 1em 20px;
     }
+  }
+}
 
-    article {
-      ul:not(.no-padding) {
-        padding: 0 20px;
-      }
+@media screen and (max-width: 480px) {
+  #main {
+    .container,
+    .has-side-nav.container {
+      display: block;
     }
   }
 }
diff --git a/types/layouts.ts b/types/layouts.ts
index 309be91ede61c..1f5576b7e880a 100644
--- a/types/layouts.ts
+++ b/types/layouts.ts
@@ -1,6 +1,7 @@
 // @TODO: These are legacy layouts that are going to be replaced with the `nodejs/nodejs.dev` Layouts in the future
 export type LegacyLayouts =
   | 'about.hbs'
+  | 'learn.hbs'
   | 'blog-index.hbs'
   | 'blog-post.hbs'
   | 'category-index.hbs'
@@ -9,5 +10,4 @@ export type LegacyLayouts =
   | 'docs.hbs'
   | 'download.hbs'
   | 'download-current.hbs'
-  | 'download-releases.hbs'
   | 'page.hbs';
diff --git a/types/navigation.ts b/types/navigation.ts
index 62210759adcb1..27ca83789ca86 100644
--- a/types/navigation.ts
+++ b/types/navigation.ts
@@ -4,6 +4,7 @@ export type NavigationKeys =
   | 'docs'
   | 'getInvolved'
   | 'certification'
+  | 'learn'
   | 'blog';
 
 export interface NavigationEntry {